proc: use the same treatment to check proc_lseek as ones for proc_read_iter et.al
- 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.1.148, 6.6.102, 6.12.42, 6.15.10, 6.16.1
- 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: proc: use the same treatment to check proc_lseek as ones for proc_read_iter et.al Check pde->proc_ops->proc_lseek directly may cause UAF in rmmod scenario. It's a gap in proc_reg_open() after commit 654b33ada4ab("proc: fix UAF in proc_get_inode()"). Followed by AI Viro's suggestion, fix it in same manner.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 3f61631d47f115b83c935d0039f95cb68b0c8ab7 · fixed in c35b0feb80b48720dfbbf4e33759c7be3faaebb6; From 3f61631d47f115b83c935d0039f95cb68b0c8ab7 · fixed in 33c778ea0bd0fa62ff590497e72562ff90f82b13; From 3f61631d47f115b83c935d0039f95cb68b0c8ab7 · fixed in fc1072d934f687e1221d685cf1a49a5068318f34; From 3f61631d47f115b83c935d0039f95cb68b0c8ab7 · fixed in d136502e04d8853a9aecb335d07bbefd7a1519a8; From 3f61631d47f115b83c935d0039f95cb68b0c8ab7 · fixed in 1fccbfbae1dd36198dc47feac696563244ad81d3; From 3f61631d47f115b83c935d0039f95cb68b0c8ab7 · fixed in ff7ec8dc1b646296f8d94c39339e8d3833d16c05
- Linux Linux
6.0
- KernelLinux
From 6.0.0 · fixed in 6.1.148; From 6.2.0 · fixed in 6.6.102; From 6.7.0 · fixed in 6.12.42; From 6.13.0 · fixed in 6.15.10; From 6.16.0 · fixed in 6.16.1