Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-40118: scsi: pm80xx: Fix array-index-out-of-of-bounds on rmmod

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.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 251be2f6037fb7ab399f68cd7428ff274133d693, 45acbf154befedd9bc135f5e031fe7855d1e6493, 5.10.246.

Low priority for now. Upgrade to Linux Linux 251be2f6037fb7ab399f68cd7428ff274133d693, 45acbf154befedd9bc135f5e031fe7855d1e6493, 5.10.246 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: scsi: pm80xx: Fix array-index-out-of-of-bounds on rmmod Since commit f7b705c238d1 ("scsi: pm80xx: Set phy_attached to zero when device is gone") UBSAN reports: UBSAN: array-index-out-of-bounds in drivers/scsi/pm8001/pm8001_sas.c:786:17 index 28 is out of range for type 'pm8001_phy [16]' on rmmod when using an expander. For a direct attached device, attached_phy contains the local phy id. For a device behind an expander, attached_phy contains the remote phy id, not the local phy id. I.e. while pm8001_ha will have pm8001_ha->chip->n_phy local phys, for a device behind an expander, attached_phy can be much larger than pm8001_ha->chip->n_phy (depending on the amount of phys of the expander). E.g. on my system pm8001_ha has 8 phys with phy ids 0-7. One of the ports has an expander connected. The expander has 31 phys with phy ids 0-30. The pm8001_ha->phy array only contains the phys of the HBA. It does not contain the phys of the expander. Thus, it is wrong to use attached_phy to index the pm8001_ha->phy array for a device behind an expander. Thus, we can only clear phy_attached for devices that are directly attached.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Nov 12, 2025
Updated
Oct 19, 2026
EPSS
0.1% · 5th percentile
CWE
—

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%

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

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

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.

—

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

    • 722026c010fa75bcf9e2373aff1d7930a3d7e3cf, 6.15affected
    • 05b512879eab41faa515b67fa3896d0005e97909 and later · before d94be0a6ae9ade706d4270e740bdb4f79953a7fcaffected · git
    • bc2140c8136200b4437e1abc0fb659968cb9baab and later · before 45acbf154befedd9bc135f5e031fe7855d1e6493affected · git
    • 1d8f9378cb4800c18e20d80ecd605b2b93e87a03 and later · before eef5ef400893f8e3dbb09342583be0cdc716d566affected · git
    • 30e482dfb8f27d22f518695d4bcb5e7f4c6cb08a and later · before 9c671d4dbfbfb0d73cfdfb706afb36d9ad60a582affected · git
    • a862d24e1fc3ab1b5e5f20878d2898cea346d0ec and later · before e62251954a128a2d0fcbc19e5fa39e08935bb628affected · git
    • 0f9802f174227f553959422f844eeb9ba72467fe and later · before 9326a1541e1b7ed3efdbab72061b82cf01c6477aaffected · git
    • f7b705c238d1483f0a766e2b20010f176e5c0fb7 and later · before 83ced3c206c292458e47c7fac54223abc7141585affected · git
    • f7b705c238d1483f0a766e2b20010f176e5c0fb7 and later · before 251be2f6037fb7ab399f68cd7428ff274133d693affected · git
    • 5.4.293 and later · before 5.4.301affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.158-16.1.158-1
Debian:13linuxbefore 6.12.57-16.12.57-1
Debian:14linuxbefore 6.17.6-16.17.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-40116Nov 12, 2025 · usb: host: max3421-hcd: Fix error pointer dereference in probe cleanup
    0Monitor
  • ← EarlierCVE-2025-40117Nov 12, 2025 · misc: pci_endpoint_test: Fix array underflow in pci_endpoint_test_ioctl()
    31Monitor
  • Later →CVE-2025-40119Nov 12, 2025 · ext4: fix potential null deref in ext4_mb_init()
    0Monitor

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 Linux251be2f6037fb7ab399f68cd7428ff274133d693Vendor (CNA)
Linux Linux45acbf154befedd9bc135f5e031fe7855d1e6493Vendor (CNA)
Linux Linux5.10.246Vendor (CNA)
Linux Linux5.15.195Vendor (CNA)
Linux Linux5.4.301Vendor (CNA)
Linux Linux6.1.156Vendor (CNA)
Linux Linux6.12.53Vendor (CNA)
Linux Linux6.15Vendor (CNA)
Linux Linux6.6.112Vendor (CNA)
Linux Linux83ced3c206c292458e47c7fac54223abc7141585Vendor (CNA)
Linux Linux9326a1541e1b7ed3efdbab72061b82cf01c6477aVendor (CNA)
Linux Linux9c671d4dbfbfb0d73cfdfb706afb36d9ad60a582Vendor (CNA)
Linux Linuxd94be0a6ae9ade706d4270e740bdb4f79953a7fcVendor (CNA)
Linux Linuxe62251954a128a2d0fcbc19e5fa39e08935bb628Vendor (CNA)
Linux Linuxeef5ef400893f8e3dbb09342583be0cdc716d566Vendor (CNA)
debian:linux6.1.158-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)

—

CVSS vector

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

nvd-secondary

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 (7 more)

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

All records