{"id":"CVE-2026-72340","aliases":[],"url":"https://o3.security/vulnerability/CVE-2026-72340","summary":"net: microchip: vcap: fix races on the shared Super VCAP block","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet: microchip: vcap: fix races on the shared Super VCAP block\n\nThe VCAP instances on a chip are not independent, yet they are locked\nindependently. On sparx5 and lan969x the IS0 and IS2 instances are\nbacked by the same Super VCAP hardware block and share its cache and\ncommand registers: every access drives the shared VCAP_SUPER_CTRL\nregister and moves data through the shared cache registers.\n\nAccessing one instance therefore races with accessing another. The\nper-instance admin->lock cannot prevent this, as each instance takes a\ndifferent lock.\n\nThe locking issue is mostly disguised by the fact that the core usage of\nthe vcap api runs under rtnl. However, the full rule dump in debugfs\ndecodes rules straight from hardware (a READ command followed by a cache\nread) and runs outside rtnl, so it races a concurrent tc-flower rule\nwrite to another Super VCAP instance.\n\nBesides corrupting the dump, the read repopulates the shared cache\nbetween the writers cache fill and its write command, so the writer\ncommits the wrong data and corrupts the hardware entry.\n\nIntroduce vcap_lock() and vcap_unlock() helpers and route every rule\nlock site in the VCAP API and its debugfs code through them. Replace the\nper-instance admin->lock with a single mutex in struct vcap_control that\nserializes access to all instances. The helpers reach it through a new\nadmin->vctrl back-pointer, and the clients initialise and destroy the\ncontrol lock instead of a per-instance one.\n\nNo path holds more than one instance lock, so collapsing them onto a\nsingle mutex cannot self-deadlock.","published":"2026-08-15T05:55:47.119Z","modified":"2026-08-18T03:56:55.543106254Z","cvss":{"score":7.8,"severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"},"epss":null,"cisaKev":null,"exploitsKnown":null,"affectedPackages":[{"ecosystem":"Linux","name":"Kernel","fixedVersion":"6.6.145"}],"fix":null,"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/1e71a40d101547380590db582213c1f1dce1f041"},{"type":"WEB","url":"https://git.kernel.org/stable/c/49806bef9572a2e012610517bc14ed0a4db0d1fc"},{"type":"WEB","url":"https://git.kernel.org/stable/c/786456d0a244bbd405dfc60e4de51f8b348b9cb1"},{"type":"WEB","url":"https://git.kernel.org/stable/c/952928564cc5fdb06f92d7e25c6cd2e1d816362b"},{"type":"WEB","url":"https://git.kernel.org/stable/c/d7a8d500d7e42837bd8dce40cb52c97c6e8706a9"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/72xxx/CVE-2026-72340.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72340"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"provenance":{"sources":["OSV.dev","FIRST.org (EPSS)"],"lastVerified":"2026-08-18T03:56:55.543106254Z"}}