bpf: Tighten cgroup storage cookie checks for prog arrays
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.17, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: bpf: Tighten cgroup storage cookie checks for prog arrays The fix in commit abad3d0bad72 ("bpf: Fix oob access in cgroup local storage") is still incomplete. The prog-array compatibility check treats a program with no cgroup storage as compatible with any stored storage cookie. This allows a storage-less program to bridge a tail call chain between an entry program and a storage-using callee even though cgroup local storage at runtime still follows the caller's context, that is, A -> B(no storage) -> C(storage) path. Requiring exact cookie equality would break the legitimate case of a storage-less leaf program being tail called from a storage-using one. Instead, only accept a zero storage cookie if the program cannot perform tail calls itself. This keeps A -> B(no storage) working while rejecting the A -> B(no storage) -> C(storage) bridge.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From c1c74584b9b4043c52e41fec415226e582d266a3 · fixed in 87177497cca90bf4fcfb759eb898560eb5b46a10; From 66da7cee78590259b400e51a70622ccd41da7bb2 · fixed in 1c762d28698483ce7c372091f34d86e4d4828652; From 7acfa07c585e3d7a64654d38f0a5c762877d0b9b · fixed in eb73056ce2a6f101ddd3bdba89af6b24ebffff85; From 41688d1fc5d163a6c2c0e95c0419e2cb31a44648 · fixed in 9ca06849c4239aa2d580c54651f8588c51cb398b; From abad3d0bad72a52137e0c350c59542d75ae4f513 · fixed in 46fbafe3d2d569d828e8d24a7dbe1659f63685cf; From abad3d0bad72a52137e0c350c59542d75ae4f513 · fixed in cb22dc79528eb26a46d346c3118dbd6b14c70609; From abad3d0bad72a52137e0c350c59542d75ae4f513 · fixed in 10627ddc0167aab5c1c390a10ef461e9937aba08; From 5.15.192 · fixed in 5.15.212; From 6.1.151 · fixed in 6.1.178; From 6.6.105 · fixed in 6.6.145; From 6.12.46 · fixed in 6.12.97; From 6.16.1 · fixed in 6.17
- Linux Linux
6.17
- KernelLinux
fixed in 5.15.212; From 5.16.0 · fixed in 6.1.178; From 6.2.0 · fixed in 6.6.145; From 6.7.0 · fixed in 6.12.97; From 6.13.0 · fixed in 6.18.40; From 6.17.0 · fixed in 7.1.5
References 7
git.kernel.org
- stable/c/87177497cca90bf4fcfb759eb898560eb5b46a10
- stable/c/1c762d28698483ce7c372091f34d86e4d4828652
- stable/c/eb73056ce2a6f101ddd3bdba89af6b24ebffff85
- stable/c/9ca06849c4239aa2d580c54651f8588c51cb398b
- stable/c/46fbafe3d2d569d828e8d24a7dbe1659f63685cf
- stable/c/cb22dc79528eb26a46d346c3118dbd6b14c70609
- stable/c/10627ddc0167aab5c1c390a10ef461e9937aba08