LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52600: jfs: fix uaf in jfs_evict_inode

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2023-52600 is a Linux kernel bug in the JFS filesystem code. Under an error path, the kernel may reuse memory after it has been freed. Public sources do not provide CVSS, confirmed impact, or active exploitation evidence. Treat it as a kernel maintenance risk, especially where JFS is enabled or mounted.

Executive priority

Handle through normal-to-elevated kernel patch management. Escalate priority for internet-facing, multi-user, or untrusted-file-processing Linux systems using JFS. Current public evidence does not justify emergency response solely for exploitation, but kernel memory bugs should not remain unpatched.

Technical view

The flaw is a use-after-free in jfs_evict_inode. If diMount(ipimap) fails, ipimap may be asynchronously released by RCU via jfs_free_node, but later accessed in diFreeSpecial. The fix avoids initializing sbi->ipimap to ipimap when diMount fails. Linux stable commits and Debian LTS advisories are listed.

Likely exposure

Exposure is most likely on Linux systems running affected kernels with JFS support available, especially systems mounting or processing JFS filesystems. The source bundle lists Linux kernel versions and stable commit references but does not provide a complete vendor-by-vendor affected matrix.

Exploitation context

No CISA KEV listing is indicated, and the provided sources do not report active exploitation. Public details describe a kernel memory-safety flaw, but not a practical attack path, required privileges, or likely impact such as crash or privilege escalation.

Researcher notes

Evidence is limited: no CVSS, CWE, exploitation report, or detailed impact assessment is provided. The core condition is an error-handling lifetime bug involving ipimap, diMount failure, RCU freeing, and diFreeSpecial access. Validate against exact downstream kernel packages, not only upstream version numbers.

Mitigation direction

  • Apply kernel updates from your Linux distribution or vendor.
  • Prioritize systems that enable or mount JFS filesystems.
  • Review Debian LTS advisories if using affected Debian releases.
  • If no package is available, track the referenced Linux stable fixes.
  • Consider disabling unused JFS support per vendor guidance.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Check whether JFS support is built, loaded, or used.
  • Compare installed kernels against vendor advisories and stable fix levels.
  • Confirm Debian systems have relevant LTS kernel updates installed.
  • Document exceptions where vendor guidance is still pending.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-52600 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
11Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2unaffected
LinuxLinux2.6.12, 0, 4.19.307, 5.4.269, 5.10.210, 5.15.149, 6.1.77, 6.6.16, 6.7.4, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.