LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26878: quota: Fix potential NULL pointer dereference

In the Linux kernel, the following vulnerability has been resolved: quota: Fix potential NULL pointer dereference Below race may cause NULL pointer dereference P1 P2 dquot_free_inode quota_off drop_dquot_ref remove_dquot_ref dquots = i_dquot(inode) dquots = i_dquot(inode) srcu_read_lock dquots[cnt]) != NULL (1) dquots[type] = NULL (2) spin_lock(&dquots[cnt]->dq_dqb_lock) (3) .... If dquot_free_inode(or other routines) checks inode's quota pointers (1) before quota_off sets it to NULL(2) and use it (3) after that, NULL pointer dereference will be triggered. So let's fix it by using a temporary pointer to avoid this issue.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-26878 is a Linux kernel quota bug that can trigger a NULL pointer dereference during a race between freeing inode quota data and turning quotas off. The public sources describe a kernel crash condition, not data theft or remote code execution. No KEV listing or supplied source indicates active exploitation.

Executive priority

Treat this as a routine but real kernel stability issue. It warrants normal patch-cycle priority, elevated for multi-tenant Linux hosts, quota-heavy storage servers, or affected appliances. Current sources do not justify emergency response based on exploitation evidence.

Technical view

The race is between dquot_free_inode or similar routines reading inode quota pointers and quota_off/drop_dquot_ref clearing them. A stale check can be followed by use after the pointer becomes NULL, leading to dereference under dq_dqb_lock handling. Kernel stable commits fix this by using a temporary pointer.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions or downstream builds that include the vulnerable quota code. Risk is most relevant where filesystem quotas are enabled or quota-off operations can occur. Appliances and distributions should be checked against vendor advisories and kernel backports.

Exploitation context

The bundle does not provide CVSS, CWE, proof of exploitation, or KEV status. The described impact is a NULL pointer dereference race, which most commonly maps to local denial of service. Do not assume remote reachability from these sources alone.

Researcher notes

The key condition is a concurrency window where i_dquot pointers are checked before quota_off nulls them and then used afterward. Analysis should focus on branch-specific backports because the CVE lists multiple stable commit references and downstream advisories rather than one universal package version.

Mitigation direction

  • Update to a kernel or vendor package containing the referenced stable quota fix.
  • Check Debian LTS and appliance vendor advisories for backported package names and versions.
  • Prioritize systems using filesystem quotas or exposing quota administration to less-trusted operators.
  • If no vendor fix is available, monitor vendor guidance and reduce unnecessary quota-off operations.

Validation and detection

  • Inventory Linux kernel versions and downstream vendor kernel package releases.
  • Confirm whether filesystem quotas are enabled on production filesystems.
  • Verify the relevant stable commit or vendor backport is present.
  • Review kernel logs for quota-related NULL pointer dereference crashes.
  • Track Debian LTS and Siemens advisories if those products are in scope.
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-26878 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
3ADP providers
14Source 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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7b9ca4c61bc278b771fb57d6290a31ab1fc7fdac, 7b9ca4c61bc278b771fb57d6290a31ab1fc7fdac, 7b9ca4c61bc278b771fb57d6290a31ab1fc7fdac, 7b9ca4c61bc278b771fb57d6290a31ab1fc7fdac, 7b9ca4c61bc278b771fb57d6290a31ab1fc7fdac, 7b9ca4c61bc278b771fb57d6290a31ab1fc7fdac, 7b9ca4c61bc278b771fb57d6290a31ab1fc7fdac, 7b9ca4c61bc278b771fb57d6290a31ab1fc7fdac, 7b9ca4c61bc278b771fb57d6290a31ab1fc7fdacunaffected
LinuxLinux4.14, 0, 4.19.311, 5.4.273, 5.10.214, 5.15.153, 6.1.83, 6.6.23, 6.7.11, 6.8.2, 6.9affected
Weakness

CWE details

No CWE listed

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