futex: Also allocate private hash on vfork()
- 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.18.54, 7.1, 7.2.8
- 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
Summary
In the Linux kernel, the following vulnerability has been resolved: futex: Also allocate private hash on vfork() As Jann demonstrated, it is entirely feasible to access the mm through vfork(). Therefore we need to allocate a private hash on vfork() as well as any other CLONE_VM user. Specifically, it must be avoided to have (private) futex waiters before allocating the private hash.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 1dcd36420af2da5bd59306dba9caf78e3d248b1d · fixed in 5468a4855b63b30156a79e5248e01bf1a2c18dd7; From ee9dce44362b2d8132c32964656ab6dff7dfbc6a · fixed in eecbafa8cabbc4d1482f6a5e2acc25a8f934681b; From ee9dce44362b2d8132c32964656ab6dff7dfbc6a · fixed in b61b6f95d6722ddbbbd09e689fa41b55fd36f9a5; From 6.18.33 · fixed in 6.18.54; From 7.0.10 · fixed in 7.1
- Linux Linux
7.1
- KernelLinux
fixed in 6.18.54; From 6.19.0 · fixed in 7.2.8