Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-21799: net: ethernet: ti: am65-cpsw: fix freeing IRQ in am65_cpsw_nuss_remove_tx_chns()

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.22% (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 321990fdf4f1bb64e818c7140688bf33d129e48d, 4395a44acb15850e492dd1de9ec4b6479d96bc80, 8448c87b3af68bebca21e3136913f7f77e363515.

Low priority for now. Upgrade to Linux Linux 321990fdf4f1bb64e818c7140688bf33d129e48d, 4395a44acb15850e492dd1de9ec4b6479d96bc80, 8448c87b3af68bebca21e3136913f7f77e363515 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: ethernet: ti: am65-cpsw: fix freeing IRQ in am65_cpsw_nuss_remove_tx_chns() When getting the IRQ we use k3_udma_glue_tx_get_irq() which returns negative error value on error. So not NULL check is not sufficient to deteremine if IRQ is valid. Check that IRQ is greater then zero to ensure it is valid. There is no issue at probe time but at runtime user can invoke .set_channels which results in the following call chain. am65_cpsw_set_channels() am65_cpsw_nuss_update_tx_rx_chns() am65_cpsw_nuss_remove_tx_chns() am65_cpsw_nuss_init_tx_chns() At this point if am65_cpsw_nuss_init_tx_chns() fails due to k3_udma_glue_tx_get_irq() then tx_chn->irq will be set to a negative value. Then, at subsequent .set_channels with higher channel count we will attempt to free an invalid IRQ in am65_cpsw_nuss_remove_tx_chns() leading to a kernel warning. The issue is present in the original commit that introduced this driver, although there, am65_cpsw_nuss_update_tx_rx_chns() existed as am65_cpsw_nuss_update_tx_chns().

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Feb 27, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 13th 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-2025-21799

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.7 and later · before 5.10.235
  • linux linux kernel5.11 and later · before 5.15.179
  • linux linux kernel5.16 and later · before 6.1.129
  • linux linux kernel6.2 and later · before 6.6.76
  • linux linux kernel6.7 and later · before 6.12.13
  • linux linux kernel6.13 and later · before 6.13.2

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.7affected
    • 93a76530316a3d8cc2d82c3deca48424fee92100 and later · before 321990fdf4f1bb64e818c7140688bf33d129e48daffected · git
    • 93a76530316a3d8cc2d82c3deca48424fee92100 and later · before ed8c0300f302338c36edb06bca99051e5be6fb2faffected · git
    • 93a76530316a3d8cc2d82c3deca48424fee92100 and later · before aea5cca681d268f794fa2385f9ec26a5cce025cdaffected · git
    • 93a76530316a3d8cc2d82c3deca48424fee92100 and later · before 88fd5db8c0073bd91d18391feb5741aeb0a2b475affected · git
    • 93a76530316a3d8cc2d82c3deca48424fee92100 and later · before 8448c87b3af68bebca21e3136913f7f77e363515affected · git
    • 93a76530316a3d8cc2d82c3deca48424fee92100 and later · before 8aae91ae1c65782a169ec070e023d4d269e5d6e6affected · git
    • 93a76530316a3d8cc2d82c3deca48424fee92100 and later · before 4395a44acb15850e492dd1de9ec4b6479d96bc80affected · git
    • before 5.7not affected · semver
    • 5.10.235 and later · up to and including 5.10.*not 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.129-16.1.129-1
Debian:13linuxbefore 6.12.13-16.12.13-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-2024-58042Feb 27, 2025 · rhashtable: Fix potential deadlock by moving schedule_work outside lock
    22Monitor
  • ← EarlierCVE-2025-21798Feb 27, 2025 · firewire: test: Fix potential null dereference in firewire kunit test
    22Monitor
  • Later →CVE-2025-21800Feb 27, 2025 · net/mlx5: HWS, fix definer's HWS_SET32 macro for negative offset
    31Monitor

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 Linux321990fdf4f1bb64e818c7140688bf33d129e48dVendor (CNA)
Linux Linux4395a44acb15850e492dd1de9ec4b6479d96bc80Vendor (CNA)
Linux Linux8448c87b3af68bebca21e3136913f7f77e363515Vendor (CNA)
Linux Linux88fd5db8c0073bd91d18391feb5741aeb0a2b475Vendor (CNA)
Linux Linux8aae91ae1c65782a169ec070e023d4d269e5d6e6Vendor (CNA)
Linux Linuxaea5cca681d268f794fa2385f9ec26a5cce025cdVendor (CNA)
Linux Linuxed8c0300f302338c36edb06bca99051e5be6fb2fVendor (CNA)
debian:linux6.1.129-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.

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. Fix✗ → ✓

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

References

Show all references (8 more)

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

All records