CVE-2023-52600
jfs: fix uaf in jfs_evict_inode
- 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
- 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
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: jfs: fix uaf in jfs_evict_inode When the execution of diMount(ipimap) fails, the object ipimap that has been released may be accessed in diFreeSpecial(). Asynchronous ipimap release occurs when rcu_core() calls jfs_free_node(). Therefore, when diMount(ipimap) fails, sbi->ipimap should not be initialized as ipimap.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
2.6.12
References 8
git.kernel.org
- stable/c/81b4249ef37297fb17ba102a524039a05c6c5d35
- stable/c/93df0a2a0b3cde2d7ab3a52ed46ea1d6d4aaba5f
- stable/c/bc6ef64dbe71136f327d63b2b9071b828af2c2a8
- stable/c/8e44dc3f96e903815dab1d74fff8faafdc6feb61
- stable/c/32e8f2d95528d45828c613417cb2827d866cbdce
- stable/c/1696d6d7d4a1b373e96428d0fe1166bd7c3c795e
- stable/c/bacdaa04251382d7efd4f09f9a0686bfcc297e2e
- stable/c/e0e1958f4c365e380b17ccb35617345b31ef7bf3