Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-23155: net: stmmac: Fix accessing freed irq affinity_hint

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.20% (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 2fbf67ddb8a0d0efc00d2df496a9843ec318d48b, 442312c2a90d60c7a5197246583fa91d9e579985, 960dab23f6d405740c537d095f90a4ee9ddd9285; azl3 kernel 6.6.112.1-2 on Azure Linux 3.0 6.6.117.1-1; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes.

Low priority for now. Upgrade to Linux Linux 2fbf67ddb8a0d0efc00d2df496a9843ec318d48b, 442312c2a90d60c7a5197246583fa91d9e579985, 960dab23f6d405740c537d095f90a4ee9ddd9285; azl3 kernel 6.6.112.1-2 on Azure Linux 3.0 6.6.117.1-1; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes 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: net: stmmac: Fix accessing freed irq affinity_hint In stmmac_request_irq_multi_msi(), a pointer to the stack variable cpu_mask is passed to irq_set_affinity_hint(). This value is stored in irq_desc->affinity_hint, but once stmmac_request_irq_multi_msi() returns, the pointer becomes dangling. The affinity_hint is exposed via procfs with S_IRUGO permissions, allowing any unprivileged process to read it. Accessing this stale pointer can lead to: - a kernel oops or panic if the referenced memory has been released and unmapped, or - leakage of kernel data into userspace if the memory is re-used for other purposes. All platforms that use stmmac with PCI MSI (Intel, Loongson, etc) are affected.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 1, 2025
Updated
Aug 5, 2026
EPSS
0.2% · 11th percentile
CWE
—

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%

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-23155

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

Affected versions

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

  • linux linux kernel5.13 and later · before 6.12.36
  • linux linux kernel6.13 and later · before 6.13.12
  • linux linux kernel6.14 and later · before 6.14.3

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

    • 5.13affected
    • 8deec94c6040bb4a767f6e9456a0a44c7f2e713e and later · before 2fbf67ddb8a0d0efc00d2df496a9843ec318d48baffected · git
    • 8deec94c6040bb4a767f6e9456a0a44c7f2e713e and later · before 960dab23f6d405740c537d095f90a4ee9ddd9285affected · git
    • 8deec94c6040bb4a767f6e9456a0a44c7f2e713e and later · before 442312c2a90d60c7a5197246583fa91d9e579985affected · git
    • 8deec94c6040bb4a767f6e9456a0a44c7f2e713e and later · before e148266e104fce396ad624079a6812ac3a9982efaffected · git
    • 8deec94c6040bb4a767f6e9456a0a44c7f2e713e and later · before 9e51a6a44e2c4de780a26e8fe110d708e806a8cdaffected · git
    • 8deec94c6040bb4a767f6e9456a0a44c7f2e713e and later · before c60d101a226f18e9a8f01bb4c6ca2b47dfcb15efaffected · git
    • before 5.13not affected · semver
    • 6.1.164 and later · up to and including 6.1.*not affected · semver
    • 6.6.117 and later · up to and including 6.6.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:11linux-6.1before 6.1.164-1~deb11u16.1.164-1~deb11u1
Debian:12linuxbefore 6.1.164-16.1.164-1
Debian:13linuxbefore 6.12.37-16.12.37-1

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-23152May 1, 2025 · arm64/crc-t10dif: fix use of out-of-scope array in crc_t10dif_arch()
    22Monitor
  • ← EarlierCVE-2025-23153May 1, 2025 · arm/crc-t10dif: fix use of out-of-scope array in crc_t10dif_arch()
    22Monitor
  • Later →CVE-2025-23156May 1, 2025 · media: venus: hfi_parser: refactor hfi packet parsing logic
    28Monitor

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 Linux2fbf67ddb8a0d0efc00d2df496a9843ec318d48bVendor (CNA)
Linux Linux442312c2a90d60c7a5197246583fa91d9e579985Vendor (CNA)
Linux Linux960dab23f6d405740c537d095f90a4ee9ddd9285Vendor (CNA)
Linux Linux9e51a6a44e2c4de780a26e8fe110d708e806a8cdVendor (CNA)
Linux Linuxc60d101a226f18e9a8f01bb4c6ca2b47dfcb15efVendor (CNA)
Linux Linuxe148266e104fce396ad624079a6812ac3a9982efVendor (CNA)
azl3 kernel 6.6.112.1-2 on Azure Linux 3.06.6.117.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0Release NotesMicrosoft (MSRC)
debian:linux6.1.164-1 · Debian:12Package registry (OSV)
debian:linux-6.16.1.164-1~deb11u1 · Debian:11Package 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.

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)

—

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

Show all references (5 more)

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

All records