CVE-2023-52600

jfs: fix uaf in jfs_evict_inode

HIGH

7.8

CVSS Score

Published: March 6, 2024 at 06:45 AM UTC

Updated: August 5, 2026 at 09:25 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.8

Exploit prediction

EPSS 0.3%

SSVC

No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v < 4.19.3072.6.12 ≤ v < 4.19.3072.6.12 ≤ v < 5.10.2102.6.12 ≤ v < 5.15.1492.6.12 ≤ v < 5.4.2692.6.12 ≤ v < 6.1.772.6.12 ≤ v < 6.6.162.6.12 ≤ v < 6.7.42.6.12 ≤ v < 6.84.20 ≤ v < 5.4.2695.11 ≤ v < 5.15.1495.16 ≤ v < 6.1.775.5 ≤ v < 5.10.2106.2 ≤ v < 6.6.166.7 ≤ v < 6.7.41da177e4c3f41524e886b7f1b8a0c1fc7321cac2 2.6.12

Vendor states this is fixed in 1696d6d7d4a1b373e96428d0fe1166bd7c3c795e (fixed)

Vendor states this is fixed in 32e8f2d95528d45828c613417cb2827d866cbdce (fixed)

Vendor states this is fixed in 81b4249ef37297fb17ba102a524039a05c6c5d35 (fixed)

Vendor states this is fixed in 8e44dc3f96e903815dab1d74fff8faafdc6feb61 (fixed)

Vendor states this is fixed in 93df0a2a0b3cde2d7ab3a52ed46ea1d6d4aaba5f (fixed)

Vendor states this is fixed in bacdaa04251382d7efd4f09f9a0686bfcc297e2e (fixed)

Vendor states this is fixed in bc6ef64dbe71136f327d63b2b9071b828af2c2a8 (fixed)

Vendor states this is fixed in e0e1958f4c365e380b17ccb35617345b31ef7bf3 (fixed)

Vendor states this is fixed in 2.6.12 (unaffected)

Vendor states this is fixed in 4.19.307 (unaffected)

Vendor states this is fixed in 5.10.210 (unaffected)

Vendor states this is fixed in 5.15.149 (unaffected)

Vendor states this is fixed in 5.4.269 (unaffected)

Vendor states this is fixed in 6.1.77 (unaffected)

Vendor states this is fixed in 6.6.16 (unaffected)

Vendor states this is fixed in 6.7.4 (unaffected)

Vendor states this is fixed in 6.8 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references