Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-38538: dmaengine: nbpfaxi: Fix memory corruption in probe()

Noroxi assessment

Priority: Monitor (action score 31/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.17% (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 122160289adf8ebf15060f1cbf6265b55a914948, 188c6ba1dd925849c5d94885c8bbdeb0b3dcf510, 24861ef8b517a309a4225f2793be0cd8fa0bec9e.

Low priority for now. Upgrade to Linux Linux 122160289adf8ebf15060f1cbf6265b55a914948, 188c6ba1dd925849c5d94885c8bbdeb0b3dcf510, 24861ef8b517a309a4225f2793be0cd8fa0bec9e 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: dmaengine: nbpfaxi: Fix memory corruption in probe() The nbpf->chan[] array is allocated earlier in the nbpf_probe() function and it has "num_channels" elements. These three loops iterate one element farther than they should and corrupt memory. The changes to the second loop are more involved. In this case, we're copying data from the irqbuf[] array into the nbpf->chan[] array. If the data in irqbuf[i] is the error IRQ then we skip it, so the iterators are not in sync. I added a check to ensure that we don't go beyond the end of the irqbuf[] array. I'm pretty sure this can't happen, but it seemed harmless to add a check. On the other hand, after the loop has ended there is a check to ensure that the "chan" iterator is where we expect it to be. In the original code we went one element beyond the end of the array so the iterator wasn't in the correct place and it would always return -EINVAL. However, now it will always be in the correct place. I deleted the check since we know the result.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Aug 16, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 7th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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

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.241
  • linux linux kernel5.11 and later · before 5.15.190
  • linux linux kernel5.16 and later · before 6.1.147
  • linux linux kernel3.17 and later · before 5.4.297
  • linux linux kernel6.7 and later · before 6.12.40
  • linux linux kernel6.13 and later · before 6.15.8
  • linux linux kernel6.2 and later · before 6.6.100
  • linux linux kernel6.16

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.17affected
    • b45b262cefd5b8eb2ba88d20e5bd295881293894 and later · before 84fff8e6f11b9af1407e273995b5257d99ff0cffaffected · git
    • b45b262cefd5b8eb2ba88d20e5bd295881293894 and later · before aec396b4f736f3f8d2c28a9cd2924a4ada57ae87affected · git
    • b45b262cefd5b8eb2ba88d20e5bd295881293894 and later · before 24861ef8b517a309a4225f2793be0cd8fa0bec9eaffected · git
    • b45b262cefd5b8eb2ba88d20e5bd295881293894 and later · before f366b36c5e3ce29c9a3c8eed3d1631908e4fc8bbaffected · git
    • b45b262cefd5b8eb2ba88d20e5bd295881293894 and later · before 4bb016438335ec02b01f96bf1367378c2bfe03e5affected · git
    • b45b262cefd5b8eb2ba88d20e5bd295881293894 and later · before 122160289adf8ebf15060f1cbf6265b55a914948affected · git
    • b45b262cefd5b8eb2ba88d20e5bd295881293894 and later · before d6bbd67ab5de37a74ac85c83c5a26664b62034ddaffected · git
    • b45b262cefd5b8eb2ba88d20e5bd295881293894 and later · before 188c6ba1dd925849c5d94885c8bbdeb0b3dcf510affected · git
    • before 3.17not 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.147-16.1.147-1
Debian:13linuxbefore 6.12.41-16.12.41-1
Debian:14linuxbefore 6.16.3-16.16.3-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-38536Aug 16, 2025 · net: airoha: fix potential use-after-free in airoha_npu_get()
    31Monitor
  • ← EarlierCVE-2025-38537Aug 16, 2025 · net: phy: Don't register LEDs for genphy
    22Monitor
  • Later →CVE-2025-38540Aug 16, 2025 · HID: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras
    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 Linux122160289adf8ebf15060f1cbf6265b55a914948Vendor (CNA)
Linux Linux188c6ba1dd925849c5d94885c8bbdeb0b3dcf510Vendor (CNA)
Linux Linux24861ef8b517a309a4225f2793be0cd8fa0bec9eVendor (CNA)
Linux Linux4bb016438335ec02b01f96bf1367378c2bfe03e5Vendor (CNA)
Linux Linux84fff8e6f11b9af1407e273995b5257d99ff0cffVendor (CNA)
Linux Linuxaec396b4f736f3f8d2c28a9cd2924a4ada57ae87Vendor (CNA)
Linux Linuxd6bbd67ab5de37a74ac85c83c5a26664b62034ddVendor (CNA)
Linux Linuxf366b36c5e3ce29c9a3c8eed3d1631908e4fc8bbVendor (CNA)
debian:linux6.1.147-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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-787 · Out-of-bounds Write

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 (9 more)

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

All records