CVE-2025-38516None▾ SunlitIn 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…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Nov 5.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
0.2% → 0.2%
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.
Linux >= f365be0925729508fd8e62f8bdb504ef896cb6e0 < 6a89563ccf9cd0d745e2291302878a061508573fLinux >= f365be0925729508fd8e62f8bdb504ef896cb6e0 < 3f8fc02c2582c1dfad1785e9c7bc8b4e1521af0aLinux >= f365be0925729508fd8e62f8bdb504ef896cb6e0 < cb4b08a095b1fa4b3fca782757517e4e9a917d8eLinux >= f365be0925729508fd8e62f8bdb504ef896cb6e0 < cc145e02d6b8494c48f91958d52fa76b7e577f7bLinux >= f365be0925729508fd8e62f8bdb504ef896cb6e0 < 1d57f7132662e96aace3b8a000616efde289aae1Linux >= f365be0925729508fd8e62f8bdb504ef896cb6e0 < 275605a8b48002fe98675a5c06f3e39c09067ff2Linux >= f365be0925729508fd8e62f8bdb504ef896cb6e0 < 97c9c7daeeb00c6e1d5e84084041f79c2d2dce22Linux >= f365be0925729508fd8e62f8bdb504ef896cb6e0 < 93712205ce2f1fb047739494c0399a26ea4f0890Linux 3.14Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99284Nonenet: skbuff: propagate shared-frag marker in skb_zerocopy()
CVE-2026-99283Nonenetfilter: conntrack: tcp: use UNACK timeout for non-closing RST packets
CVE-2026-99272Nonesmb: client: validate the data area in SMB2_read()
CVE-2026-99271NoneALSA: line6: Clear prev_fbuf on capture buffer release
CVE-2026-99273Noneksmbd: reserve space for the UTF-16 terminator in stream info
CVE-2026-99275Nonesmb: client: reject short SESSION_SETUP responses