LiveActive security incident?Get immediate response
CVE Record

CVE-2024-44939: jfs: fix null ptr deref in dtInsertEntry

In the Linux kernel, the following vulnerability has been resolved: jfs: fix null ptr deref in dtInsertEntry [syzbot reported] general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] PREEMPT SMP KASAN PTI KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f] CPU: 0 PID: 5061 Comm: syz-executor404 Not tainted 6.8.0-syzkaller-08951-gfe46a7dd189e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 RIP: 0010:dtInsertEntry+0xd0c/0x1780 fs/jfs/jfs_dtree.c:3713 ... [Analyze] In dtInsertEntry(), when the pointer h has the same value as p, after writing name in UniStrncpy_to_le(), p->header.flag will be cleared. This will cause the previously true judgment "p->header.flag & BT-LEAF" to change to no after writing the name operation, this leads to entering an incorrect branch and accessing the uninitialized object ih when judging this condition for the second time. [Fix] After got the page, check freelist first, if freelist == 0 then exit dtInsert() and return -EINVAL.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-44939 is a Linux kernel JFS filesystem bug that can trigger a null pointer dereference. In practical terms, affected systems that use or process JFS filesystems could crash or behave unpredictably. The public sources do not provide CVSS scoring or evidence of active exploitation.

Executive priority

Prioritize routine kernel patching, with higher urgency for systems that allow users, workloads, or automation to mount filesystem images. No active exploitation is cited, but kernel crashes can affect availability on shared or critical hosts.

Technical view

The flaw is in JFS dtInsertEntry(). A name copy can clear p->header.flag when h and p alias, changing BT_LEAF logic and causing access to an uninitialized ih object. Stable kernel commits add a freelist check and return -EINVAL when freelist is zero.

Likely exposure

Exposure is most likely on Linux systems where JFS support is enabled and untrusted or malformed JFS filesystem data can be mounted or processed. Organizations not using JFS have lower practical exposure, but should still track distro kernel status.

Exploitation context

The source bundle attributes discovery to syzbot and kernel sanitizers. It does not cite public exploitation, weaponized proof of concept, or CISA KEV listing. Treat this as a potential local denial-of-service or stability risk unless vendor advisories state otherwise.

Researcher notes

Evidence is limited to the CVE record, Linux stable commits, and a Debian LTS advisory. The bundle does not provide CVSS, CWE, exploitability details, or complete affected-version semantics, so validation should rely on distribution backport status.

Mitigation direction

  • Apply vendor kernel updates containing the referenced JFS stable fixes.
  • Check Debian or other distribution advisories for packaged kernel updates.
  • Disable or restrict JFS use where it is unnecessary.
  • Limit who can mount filesystems or attach block images.
  • Follow vendor guidance if running custom or long-term kernels.

Validation and detection

  • Inventory Linux kernels and identify systems with JFS enabled or loaded.
  • Compare kernel package versions against vendor fixed advisories.
  • Confirm deployed kernels include the referenced stable commits or backports.
  • Review whether users can mount or process untrusted JFS media.
  • Monitor kernel logs for JFS crashes or related oops reports.
Prepared
Confidence
medium
Sources
8

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-2024-44939 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
7Source 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2unaffected
LinuxLinux2.6.12, 0, 5.15.189, 6.1.107, 6.6.47, 6.10.6, 6.11affected
Weakness

CWE details

No CWE listed

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