net: qualcomm: rmnet: restore skb->dev on deaggregated frames
Noroxi assessment
Priority: Monitor (action score 0/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.21% (FIRST EPSS).
- Fixed version: Linux Linux 200460a0793dc6af97d3b36d92ac245350ac26fc, 4bcef54e4a3355a62d9ad90729fe563435ec76c3, 5aaa7409c1b4ca4c60d66e2afa99703bf4eb7ddd.
Low priority for now. Upgrade to Linux Linux 200460a0793dc6af97d3b36d92ac245350ac26fc, 4bcef54e4a3355a62d9ad90729fe563435ec76c3, 5aaa7409c1b4ca4c60d66e2afa99703bf4eb7ddd 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: qualcomm: rmnet: restore skb->dev on deaggregated frames rmnet_map_deaggregate() allocates each sub-frame with alloc_skb() and leaves skb->dev NULL. __rmnet_map_ingress_handler() assigns skb->dev = ep->egress_dev only on the data path, but a MAP command frame is dispatched to rmnet_map_command() before that, so rmnet_map_send_ack() runs netif_tx_lock(skb->dev) on a NULL device. An unprivileged user reaches this by unsharing a user+net namespace, creating an rmnet link over a tap device with INGRESS_DEAGGREGATION and INGRESS_MAP_COMMANDS, and writing an aggregated frame carrying a flow-control command to the tap fd. Restore the assignment dropped by 378e25357ac7, so every skb leaving rmnet_map_deaggregate() has a valid device. BUG: KASAN: null-ptr-deref in _raw_spin_lock (kernel/locking/spinlock.c:158) Write of size 4 at addr 00000000000004b4 by task exploit/144 Call Trace: _raw_spin_lock (kernel/locking/spinlock.c:158) netif_tx_lock (net/sched/sch_generic.c:497) rmnet_map_command (drivers/net/ethernet/qualcomm/rmnet/rmnet_map_command.c:67) rmnet_rx_handler (drivers/net/ethernet/qualcomm/rmnet/rmnet_handlers.c:125) __netif_receive_skb_core.constprop.0 (net/core/dev.c:6103) ... __netif_receive_skb_one_core (net/core/dev.c:6214) netif_receive_skb (net/core/dev.c:6474) tun_get_user (drivers/net/tun.c:1966) tun_chr_write_iter (drivers/net/tun.c:2012) vfs_write (fs/read_write.c:687) ksys_write (fs/read_write.c:739) do_syscall_64 (arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121) Kernel panic - not syncing: Fatal exception in interrupt
- Published
- Sep 16, 2026
- Updated
- Sep 16, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- 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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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
- 4.17affected
- 378e25357ac78ad02fbc98bec9b4e3baaa916c5c and later · before 5aaa7409c1b4ca4c60d66e2afa99703bf4eb7dddaffected · git
- 378e25357ac78ad02fbc98bec9b4e3baaa916c5c and later · before 9b78ab84ddf97c06a8567edb62b6c0fd582f9a62affected · git
- 378e25357ac78ad02fbc98bec9b4e3baaa916c5c and later · before 9d18c6c6cd1666b2cb7915cad052e22abf520997affected · git
- 378e25357ac78ad02fbc98bec9b4e3baaa916c5c and later · before 4bcef54e4a3355a62d9ad90729fe563435ec76c3affected · git
- 378e25357ac78ad02fbc98bec9b4e3baaa916c5c and later · before b14c22c31d9e30f38ea1693ac06d318f32258f5daffected · git
- 378e25357ac78ad02fbc98bec9b4e3baaa916c5c and later · before 7abe769e72c792e5f9eb273813eb3ecd8389854caffected · git
- 378e25357ac78ad02fbc98bec9b4e3baaa916c5c and later · before 200460a0793dc6af97d3b36d92ac245350ac26fcaffected · git
- 378e25357ac78ad02fbc98bec9b4e3baaa916c5c and later · before a66734a1c5e36525ea07e9f4547fddc51e916de3affected · git
- before 4.17not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89778Sep 16, 2026 · isofs: fix out-of-bounds page array access on empty zisofs block39Monitor
- ← EarlierCVE-2026-89779Sep 16, 2026 · fs/ntfs3: validate ef->size covers the record's name and value36Monitor
- Later →CVE-2026-89781Sep 16, 2026 · fs/ntfs3: fix out-of-bounds read in read_log_rec_buf()33Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 200460a0793dc6af97d3b36d92ac245350ac26fc | Vendor (CNA) |
| Linux Linux | 4bcef54e4a3355a62d9ad90729fe563435ec76c3 | Vendor (CNA) |
| Linux Linux | 5aaa7409c1b4ca4c60d66e2afa99703bf4eb7ddd | Vendor (CNA) |
| Linux Linux | 7abe769e72c792e5f9eb273813eb3ecd8389854c | Vendor (CNA) |
| Linux Linux | 9b78ab84ddf97c06a8567edb62b6c0fd582f9a62 | Vendor (CNA) |
| Linux Linux | 9d18c6c6cd1666b2cb7915cad052e22abf520997 | Vendor (CNA) |
| Linux Linux | a66734a1c5e36525ea07e9f4547fddc51e916de3 | Vendor (CNA) |
| Linux Linux | b14c22c31d9e30f38ea1693ac06d318f32258f5d | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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 researchersFinders, 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
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/4bcef54e4a3355a62d9ad90729fe563435ec76c3
- git.kernel.org/stable/c/5aaa7409c1b4ca4c60d66e2afa99703bf4eb7ddd
- git.kernel.org/stable/c/7abe769e72c792e5f9eb273813eb3ecd8389854c
- git.kernel.org/stable/c/9b78ab84ddf97c06a8567edb62b6c0fd582f9a62
- git.kernel.org/stable/c/9d18c6c6cd1666b2cb7915cad052e22abf520997
- git.kernel.org/stable/c/a66734a1c5e36525ea07e9f4547fddc51e916de3
- git.kernel.org/stable/c/b14c22c31d9e30f38ea1693ac06d318f32258f5d
Vendor advisories and official records. Exploit/PoC links are deliberately left out.