Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-53131: nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 085556bf8c70e2629e02e79268dac3016a08b8bf, 19c71cdd77973f99a9adc3190130bc3aa7ae5423, 3b2a4fd9bbee77afdd3ed5a05a0c02b6cde8d3b9; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1.

Low priority for now. Upgrade to Linux Linux 085556bf8c70e2629e02e79268dac3016a08b8bf, 19c71cdd77973f99a9adc3190130bc3aa7ae5423, 3b2a4fd9bbee77afdd3ed5a05a0c02b6cde8d3b9; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint Patch series "nilfs2: fix null-ptr-deref bugs on block tracepoints". This series fixes null pointer dereference bugs that occur when using nilfs2 and two block-related tracepoints. This patch (of 2): It has been reported that when using "block:block_touch_buffer" tracepoint, touch_buffer() called from __nilfs_get_folio_block() causes a NULL pointer dereference, or a general protection fault when KASAN is enabled. This happens because since the tracepoint was added in touch_buffer(), it references the dev_t member bh->b_bdev->bd_dev regardless of whether the buffer head has a pointer to a block_device structure. In the current implementation, the block_device structure is set after the function returns to the caller. Here, touch_buffer() is used to mark the folio/page that owns the buffer head as accessed, but the common search helper for folio/page used by the caller function was optimized to mark the folio/page as accessed when it was reimplemented a long time ago, eliminating the need to call touch_buffer() here in the first place. So this solves the issue by eliminating the touch_buffer() call itself.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Dec 4, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 14th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-53131

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel3.9 and later · before 6.1.119
  • linux linux kernel6.6.0 and later · before 6.6.63
  • linux linux kernel6.11.0 and later · before 6.11.10

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.9affected
    • 5305cb830834549b9203ad4d009ad5483c5e293f and later · before 085556bf8c70e2629e02e79268dac3016a08b8bfaffected · git
    • 5305cb830834549b9203ad4d009ad5483c5e293f and later · before 6438f3f42cda825f6f59b4e45ac3a1da28a6f2c9affected · git
    • 5305cb830834549b9203ad4d009ad5483c5e293f and later · before b017697a517f8779ada4e8ce1c2c75dbf60a2636affected · git
    • 5305cb830834549b9203ad4d009ad5483c5e293f and later · before 19c71cdd77973f99a9adc3190130bc3aa7ae5423affected · git
    • 5305cb830834549b9203ad4d009ad5483c5e293f and later · before 3b2a4fd9bbee77afdd3ed5a05a0c02b6cde8d3b9affected · git
    • 5305cb830834549b9203ad4d009ad5483c5e293f and later · before 59b49ca67cca7b007a5afd3de0283c8008157665affected · git
    • 5305cb830834549b9203ad4d009ad5483c5e293f and later · before 77e47f89d32c2d72eb33d0becbce7abe14d061f4affected · git
    • 5305cb830834549b9203ad4d009ad5483c5e293f and later · before cd45e963e44b0f10d90b9e6c0e8b4f47f3c92471affected · git
    • before 3.9not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.119-16.1.119-1
Debian:13linuxbefore 6.11.10-16.11.10-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-53129Dec 4, 2024 · drm/rockchip: vop: Fix a dereferenced before check warning
    22Monitor
  • ← EarlierCVE-2024-53130Dec 4, 2024 · nilfs2: fix null-ptr-deref in block_dirty_buffer tracepoint
    22Monitor
  • Later →CVE-2024-53132Dec 4, 2024 · drm/xe/oa: Fix "Missing outer runtime PM protection" warning
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux085556bf8c70e2629e02e79268dac3016a08b8bfVendor (CNA)
Linux Linux19c71cdd77973f99a9adc3190130bc3aa7ae5423Vendor (CNA)
Linux Linux3b2a4fd9bbee77afdd3ed5a05a0c02b6cde8d3b9Vendor (CNA)
Linux Linux59b49ca67cca7b007a5afd3de0283c8008157665Vendor (CNA)
Linux Linux6438f3f42cda825f6f59b4e45ac3a1da28a6f2c9Vendor (CNA)
Linux Linux77e47f89d32c2d72eb33d0becbce7abe14d061f4Vendor (CNA)
Linux Linuxb017697a517f8779ada4e8ce1c2c75dbf60a2636Vendor (CNA)
Linux Linuxcd45e963e44b0f10d90b9e6c0e8b4f47f3c92471Vendor (CNA)
azl3 kernel 6.6.57.1-7 on Azure Linux 3.06.6.64.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.64.2-1 on Azure Linux 3.06.6.64.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.176.3-1 on CBL Mariner 2.05.15.176.3-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.180.1-1 on CBL Mariner 2.0CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.180.1-1 on CBL-Mariner 2.05.15.176.3-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.119-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records