futex: Require sys_futex_requeue() to have identical flags
- 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 6.12.80, 6.18.21, 6.19.11
- 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: futex: Require sys_futex_requeue() to have identical flags Nicholas reported that his LLM found it was possible to create a UaF when sys_futex_requeue() is used with different flags. The initial motivation for allowing different flags was the variable sized futex, but since that hasn't been merged (yet), simply mandate the flags are identical, as is the case for the old style sys_futex() requeue operations.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 0f4b5f972216782a4acb1ae00dcb55173847c2ff · fixed in 027145ace09fad4c7cbcd6c61fe9b429c63eb0e5; From 0f4b5f972216782a4acb1ae00dcb55173847c2ff · fixed in 18b7d09c2b794c71d4252f3ea2cf84ad12b73d6a; From 0f4b5f972216782a4acb1ae00dcb55173847c2ff · fixed in e2f78c7ec1655fedd945366151ba54fcb9580508; From 0f4b5f972216782a4acb1ae00dcb55173847c2ff · fixed in 19f94b39058681dec64a10ebeb6f23fe7fc3f77a
- Linux Linux
6.7
- KernelLinux
From 6.7.0 · fixed in 6.12.80; From 6.13.0 · fixed in 6.18.21; From 6.19.0 · fixed in 6.19.11