Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-39902: mm/slub: avoid accessing metadata when pointer is invalid in object_err()

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.16% (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 0ef7058b4dc6fcef622ac23b45225db57f17b83f, 1f0797f17927b5cad0fb7eced422f9a7c30a3191, 3baa1da473e6e50281324ff1d332d1a07a3bb02e; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1.

Low priority for now. Upgrade to Linux Linux 0ef7058b4dc6fcef622ac23b45225db57f17b83f, 1f0797f17927b5cad0fb7eced422f9a7c30a3191, 3baa1da473e6e50281324ff1d332d1a07a3bb02e; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-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: mm/slub: avoid accessing metadata when pointer is invalid in object_err() object_err() reports details of an object for further debugging, such as the freelist pointer, redzone, etc. However, if the pointer is invalid, attempting to access object metadata can lead to a crash since it does not point to a valid object. One known path to the crash is when alloc_consistency_checks() determines the pointer to the allocated object is invalid because of a freelist corruption, and calls object_err() to report it. The debug code should report and handle the corruption gracefully and not crash in the process. In case the pointer is NULL or check_valid_pointer() returns false for the pointer, only print the pointer value and skip accessing metadata.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Oct 1, 2025
Updated
Oct 19, 2026
EPSS
0.1% · 6th 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.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
7.1
1.6 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-2025-39902

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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
debiandebian linux

Affected versions

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

  • debian debian linux11.0
  • linux linux kernel5.5 and later · before 5.10.243
  • linux linux kernel5.11 and later · before 5.15.192
  • linux linux kernel5.16 and later · before 6.1.151
  • linux linux kernel2.6.22 and later · before 5.4.299
  • linux linux kernel6.7 and later · before 6.12.46
  • linux linux kernel6.13 and later · before 6.16.6
  • linux linux kernel6.2 and later · before 6.6.105
  • linux linux kernel6.17

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

    • 2.6.22affected
    • 81819f0fc8285a2a5a921c019e3e3d7b6169d225 and later · before 872f2c34ff232af1e65ad2df86d61163c8ffad42affected · git
    • 81819f0fc8285a2a5a921c019e3e3d7b6169d225 and later · before f66012909e7bf383fcdc5850709ed5716073fdc4affected · git
    • 81819f0fc8285a2a5a921c019e3e3d7b6169d225 and later · before 7e287256904ee796c9477e3ec92b07f236481ef3affected · git
    • 81819f0fc8285a2a5a921c019e3e3d7b6169d225 and later · before 1f0797f17927b5cad0fb7eced422f9a7c30a3191affected · git
    • 81819f0fc8285a2a5a921c019e3e3d7b6169d225 and later · before 0ef7058b4dc6fcef622ac23b45225db57f17b83faffected · git
    • 81819f0fc8285a2a5a921c019e3e3d7b6169d225 and later · before dda6ec365ab04067adae40ef17015db447e90736affected · git
    • 81819f0fc8285a2a5a921c019e3e3d7b6169d225 and later · before 3baa1da473e6e50281324ff1d332d1a07a3bb02eaffected · git
    • 81819f0fc8285a2a5a921c019e3e3d7b6169d225 and later · before b4efccec8d06ceb10a7d34d7b1c449c569d53770affected · git
    • before 2.6.22not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.156.1.el8_104.18.0-553.156.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.156.1.el8_104.18.0-553.156.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.156.1.el8_104.18.0-553.156.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.156.1.el8_104.18.0-553.156.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.156.1.el8_104.18.0-553.156.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.156.1.el8_104.18.0-553.156.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.156.1.el8_104.18.0-553.156.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.156.1.el8_104.18.0-553.156.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.156.1.el8_104.18.0-553.156.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.156.1.el8_104.18.0-553.156.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.156.1.el8_104.18.0-553.156.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.156.1.el8_104.18.0-553.156.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.156.1.el8_104.18.0-553.156.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.156.1.el8_104.18.0-553.156.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.156.1.el8_104.18.0-553.156.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.156.1.rt7.497.el8_104.18.0-553.156.1.rt7.497.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.156.1.rt7.497.el8_104.18.0-553.156.1.rt7.497.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.156.1.rt7.497.el8_104.18.0-553.156.1.rt7.497.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.156.1.rt7.497.el8_104.18.0-553.156.1.rt7.497.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.156.1.rt7.497.el8_104.18.0-553.156.1.rt7.497.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.156.1.rt7.497.el8_104.18.0-553.156.1.rt7.497.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.156.1.rt7.497.el8_104.18.0-553.156.1.rt7.497.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.156.1.rt7.497.el8_104.18.0-553.156.1.rt7.497.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.156.1.rt7.497.el8_104.18.0-553.156.1.rt7.497.el8_10

+65

Same product

linux: all records

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-2025-39900Oct 1, 2025 · net_sched: gen_estimator: fix est_timer() vs CONFIG_PREEMPT_RT=y
    22Monitor
  • ← EarlierCVE-2025-39901Oct 1, 2025 · i40e: remove read access to debugfs files
    28Monitor
  • Later →CVE-2025-39903Oct 1, 2025 · of_numa: fix uninitialized memory nodes causing kernel panic
    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 Linux0ef7058b4dc6fcef622ac23b45225db57f17b83fVendor (CNA)
Linux Linux1f0797f17927b5cad0fb7eced422f9a7c30a3191Vendor (CNA)
Linux Linux3baa1da473e6e50281324ff1d332d1a07a3bb02eVendor (CNA)
Linux Linux7e287256904ee796c9477e3ec92b07f236481ef3Vendor (CNA)
Linux Linux872f2c34ff232af1e65ad2df86d61163c8ffad42Vendor (CNA)
Linux Linuxb4efccec8d06ceb10a7d34d7b1c449c569d53770Vendor (CNA)
Linux Linuxdda6ec365ab04067adae40ef17015db447e90736Vendor (CNA)
Linux Linuxf66012909e7bf383fcdc5850709ed5716073fdc4Vendor (CNA)
azl3 kernel 6.6.104.2-4 on Azure Linux 3.06.6.112.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.156.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.153-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-553.156.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-553.156.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-553.156.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-553.156.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-553.156.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-553.156.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-553.156.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-553.156.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)

+6

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.

Credits

All researchers

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

Weakness class (CWE)

CWE-476 · NULL Pointer Dereference

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. SSVC exploitation— → none
  2. Fix✗ → ✓

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

References

Show all references (9 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records