Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-38516: pinctrl: qcom: msm: mark certain pins as invalid for interrupts

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 1d57f7132662e96aace3b8a000616efde289aae1, 275605a8b48002fe98675a5c06f3e39c09067ff2, 3f8fc02c2582c1dfad1785e9c7bc8b4e1521af0a; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1; cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 5.15.200.1-1.

Low priority for now. Upgrade to Linux Linux 1d57f7132662e96aace3b8a000616efde289aae1, 275605a8b48002fe98675a5c06f3e39c09067ff2, 3f8fc02c2582c1dfad1785e9c7bc8b4e1521af0a; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1; cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 5.15.200.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: pinctrl: qcom: msm: mark certain pins as invalid for interrupts On some platforms, the UFS-reset pin has no interrupt logic in TLMM but is nevertheless registered as a GPIO in the kernel. This enables the user-space to trigger a BUG() in the pinctrl-msm driver by running, for example: `gpiomon -c 0 113` on RB2. The exact culprit is requesting pins whose intr_detection_width setting is not 1 or 2 for interrupts. This hits a BUG() in msm_gpio_irq_set_type(). Potentially crashing the kernel due to an invalid request from user-space is not optimal, so let's go through the pins and mark those that would fail the check as invalid for the irq chip as we should not even register them as available irqs. This function can be extended if we determine that there are more corner-cases like this.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Aug 16, 2025
Updated
Jun 17, 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%

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

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.240
  • linux linux kernel5.11 and later · before 5.15.189
  • linux linux kernel5.16 and later · before 6.1.146
  • linux linux kernel3.14 and later · before 5.4.296
  • linux linux kernel6.7 and later · before 6.12.39
  • linux linux kernel6.13 and later · before 6.15.7
  • linux linux kernel6.2 and later · before 6.6.99
  • 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.14affected
    • f365be0925729508fd8e62f8bdb504ef896cb6e0 and later · before 6a89563ccf9cd0d745e2291302878a061508573faffected · git
    • f365be0925729508fd8e62f8bdb504ef896cb6e0 and later · before 3f8fc02c2582c1dfad1785e9c7bc8b4e1521af0aaffected · git
    • f365be0925729508fd8e62f8bdb504ef896cb6e0 and later · before cb4b08a095b1fa4b3fca782757517e4e9a917d8eaffected · git
    • f365be0925729508fd8e62f8bdb504ef896cb6e0 and later · before cc145e02d6b8494c48f91958d52fa76b7e577f7baffected · git
    • f365be0925729508fd8e62f8bdb504ef896cb6e0 and later · before 1d57f7132662e96aace3b8a000616efde289aae1affected · git
    • f365be0925729508fd8e62f8bdb504ef896cb6e0 and later · before 275605a8b48002fe98675a5c06f3e39c09067ff2affected · git
    • f365be0925729508fd8e62f8bdb504ef896cb6e0 and later · before 97c9c7daeeb00c6e1d5e84084041f79c2d2dce22affected · git
    • f365be0925729508fd8e62f8bdb504ef896cb6e0 and later · before 93712205ce2f1fb047739494c0399a26ea4f0890affected · git
    • before 3.14not 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-38513Aug 16, 2025 · wifi: zd1211rw: Fix potential NULL pointer dereference in zd_mac_tx_to_dev()
    22Monitor
  • ← EarlierCVE-2025-38515Aug 16, 2025 · drm/sched: Increment job count before swapping tail spsc queue
    18Monitor
  • Later →CVE-2025-38517Aug 16, 2025 · lib/alloc_tag: do not acquire non-existent lock in alloc_tag_top_users()
    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 Linux1d57f7132662e96aace3b8a000616efde289aae1Vendor (CNA)
Linux Linux275605a8b48002fe98675a5c06f3e39c09067ff2Vendor (CNA)
Linux Linux3f8fc02c2582c1dfad1785e9c7bc8b4e1521af0aVendor (CNA)
Linux Linux6a89563ccf9cd0d745e2291302878a061508573fVendor (CNA)
Linux Linux93712205ce2f1fb047739494c0399a26ea4f0890Vendor (CNA)
Linux Linux97c9c7daeeb00c6e1d5e84084041f79c2d2dce22Vendor (CNA)
Linux Linuxcb4b08a095b1fa4b3fca782757517e4e9a917d8eVendor (CNA)
Linux Linuxcc145e02d6b8494c48f91958d52fa76b7e577f7bVendor (CNA)
azl3 kernel 6.6.96.2-2 on Azure Linux 3.06.6.104.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.05.15.200.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
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
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 (9 more)

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

All records