CVE-2025-38035: nvmet-tcp: don't restore null sk_state_change
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.57% (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.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 17e58be5b49f58bf17799a504f55c2d05ab2ecdc, 3a982ada411b8c52695f1784c3f4784771f30209, 46d22b47df2741996af277a2838b95f130436c13.
- Severity is disputed: the assigning authority (CNA) scores it 7.5, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 17e58be5b49f58bf17799a504f55c2d05ab2ecdc, 3a982ada411b8c52695f1784c3f4784771f30209, 46d22b47df2741996af277a2838b95f130436c13 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: nvmet-tcp: don't restore null sk_state_change queue->state_change is set as part of nvmet_tcp_set_queue_sock(), but if the TCP connection isn't established when nvmet_tcp_set_queue_sock() is called then queue->state_change isn't set and sock->sk->sk_state_change isn't replaced. As such we don't need to restore sock->sk->sk_state_change if queue->state_change is NULL. This avoids NULL pointer dereferences such as this: [ 286.462026][ C0] BUG: kernel NULL pointer dereference, address: 0000000000000000 [ 286.462814][ C0] #PF: supervisor instruction fetch in kernel mode [ 286.463796][ C0] #PF: error_code(0x0010) - not-present page [ 286.464392][ C0] PGD 8000000140620067 P4D 8000000140620067 PUD 114201067 PMD 0 [ 286.465086][ C0] Oops: Oops: 0010 [#1] SMP KASAN PTI [ 286.465559][ C0] CPU: 0 UID: 0 PID: 1628 Comm: nvme Not tainted 6.15.0-rc2+ #11 PREEMPT(voluntary) [ 286.466393][ C0] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014 [ 286.467147][ C0] RIP: 0010:0x0 [ 286.467420][ C0] Code: Unable to access opcode bytes at 0xffffffffffffffd6. [ 286.467977][ C0] RSP: 0018:ffff8883ae008580 EFLAGS: 00010246 [ 286.468425][ C0] RAX: 0000000000000000 RBX: ffff88813fd34100 RCX: ffffffffa386cc43 [ 286.469019][ C0] RDX: 1ffff11027fa68b6 RSI: 0000000000000008 RDI: ffff88813fd34100 [ 286.469545][ C0] RBP: ffff88813fd34160 R08: 0000000000000000 R09: ffffed1027fa682c [ 286.470072][ C0] R10: ffff88813fd34167 R11: 0000000000000000 R12: ffff88813fd344c3 [ 286.470585][ C0] R13: ffff88813fd34112 R14: ffff88813fd34aec R15: ffff888132cdd268 [ 286.471070][ C0] FS: 00007fe3c04c7d80(0000) GS:ffff88840743f000(0000) knlGS:0000000000000000 [ 286.471644][ C0] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 286.472543][ C0] CR2: ffffffffffffffd6 CR3: 000000012daca000 CR4: 00000000000006f0 [ 286.473500][ C0] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 286.474467][ C0] DR3: 0000000000000000 DR6: 00000000ffff07f0 DR7: 0000000000000400 [ 286.475453][ C0] Call Trace: [ 286.476102][ C0] <IRQ> [ 286.476719][ C0] tcp_fin+0x2bb/0x440 [ 286.477429][ C0] tcp_data_queue+0x190f/0x4e60 [ 286.478174][ C0] ? __build_skb_around+0x234/0x330 [ 286.478940][ C0] ? rcu_is_watching+0x11/0xb0 [ 286.479659][ C0] ? __pfx_tcp_data_queue+0x10/0x10 [ 286.480431][ C0] ? tcp_try_undo_loss+0x640/0x6c0 [ 286.481196][ C0] ? seqcount_lockdep_reader_access.constprop.0+0x82/0x90 [ 286.482046][ C0] ? kvm_clock_get_cycles+0x14/0x30 [ 286.482769][ C0] ? ktime_get+0x66/0x150 [ 286.483433][ C0] ? rcu_is_watching+0x11/0xb0 [ 286.484146][ C0] tcp_rcv_established+0x6e4/0x2050 [ 286.484857][ C0] ? rcu_is_watching+0x11/0xb0 [ 286.485523][ C0] ? ipv4_dst_check+0x160/0x2b0 [ 286.486203][ C0] ? __pfx_tcp_rcv_established+0x10/0x10 [ 286.486917][ C0] ? lock_release+0x217/0x2c0 [ 286.487595][ C0] tcp_v4_do_rcv+0x4d6/0x9b0 [ 286.488279][ C0] tcp_v4_rcv+0x2af8/0x3e30 [ 286.488904][ C0] ? raw_local_deliver+0x51b/0xad0 [ 286.489551][ C0] ? rcu_is_watching+0x11/0xb0 [ 286.490198][ C0] ? __pfx_tcp_v4_rcv+0x10/0x10 [ 286.490813][ C0] ? __pfx_raw_local_deliver+0x10/0x10 [ 286.491487][ C0] ? __pfx_nf_confirm+0x10/0x10 [nf_conntrack] [ 286.492275][ C0] ? rcu_is_watching+0x11/0xb0 [ 286.492900][ C0] ip_protocol_deliver_rcu+0x8f/0x370 [ 286.493579][ C0] ip_local_deliver_finish+0x297/0x420 [ 286.494268][ C0] ip_local_deliver+0x168/0x430 [ 286.494867][ C0] ? __pfx_ip_local_deliver+0x10/0x10 [ 286.495498][ C0] ? __pfx_ip_local_deliver_finish+0x10/0x10 [ 286.496204][ C0] ? ip_rcv_finish_core+0x19a/0x1f20 [ 286.496806][ C0] ? lock_release+0x217/0x2c0 [ 286.497414][ C0] ip_rcv+0x455/0x6e0 [ 286.497945][ C0] ? __pfx_ip_rcv+0x10/0x10 [ ---truncated---
- Published
- Jun 18, 2025
- Updated
- Oct 15, 2026
- EPSS
- 0.5% · 47th percentile
- CWE
- CWE-476
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.5
- 2.0 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_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.238
- linux linux kernel5.11 and later · before 5.15.185
- linux linux kernel5.16 and later · before 6.1.141
- linux linux kernel5.0 and later · before 5.4.294
- linux linux kernel6.7 and later · before 6.12.31
- linux linux kernel6.13 and later · before 6.14.9
- linux linux kernel6.2 and later · before 6.6.93
- linux linux kernel6.15
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
- 5.0affected
- 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and later · before 6265538446e2426f4bf3b57e91d7680b2047ddd9affected · git
- 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and later · before 17e58be5b49f58bf17799a504f55c2d05ab2ecdcaffected · git
- 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and later · before fc01b547c3f8bfa6e1d23cd5a2c63c736e8c3e4eaffected · git
- 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and later · before c240375587ddcc80e1022f52ee32b946bbc3a639affected · git
- 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and later · before 3a982ada411b8c52695f1784c3f4784771f30209affected · git
- 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and later · before ec462449f4cf616b0aa2ed119f5f44b5fdfcefabaffected · git
- 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and later · before a21cb31642ffc84ca4ce55028212a96f72f54d30affected · git
- 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and later · before 46d22b47df2741996af277a2838b95f130436c13affected · git
- before 5.0not 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.147-1 | 6.1.147-1 |
| Debian:13 | linux | before 6.12.32-1 | 6.12.32-1 |
| openSUSE:Leap 15.6 | kernel-rt | before 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 |
| openSUSE:Leap 15.6 | kernel-rt_debug | before 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 |
| openSUSE:Leap 15.6 | kernel-source-rt | before 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 |
| openSUSE:Leap 15.6 | kernel-syms-rt | before 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6-RT_Update_14 | before 1-150600.1.5.1 | 1-150600.1.5.1 |
| SUSE:Linux Micro 6.0 | kernel-default | before 6.4.0-32.1 | 6.4.0-32.1 |
| SUSE:Linux Micro 6.0 | kernel-default-base | before 6.4.0-32.1.21.10 | 6.4.0-32.1.21.10 |
| SUSE:Linux Micro 6.0 | kernel-kvmsmall | before 6.4.0-32.1 | 6.4.0-32.1 |
| SUSE:Linux Micro 6.0 | kernel-rt | before 6.4.0-35.1 | 6.4.0-35.1 |
| SUSE:Linux Micro 6.0 | kernel-source | before 6.4.0-32.1 | 6.4.0-32.1 |
| SUSE:Linux Micro 6.0 | kernel-source-rt | before 6.4.0-35.1 | 6.4.0-35.1 |
| SUSE:Real Time Module 15 SP6 | kernel-rt | before 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 |
| SUSE:Real Time Module 15 SP6 | kernel-rt_debug | before 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 |
| SUSE:Real Time Module 15 SP6 | kernel-source-rt | before 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 |
| SUSE:Real Time Module 15 SP6 | kernel-syms-rt | before 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38006Jun 18, 2025 · net: mctp: Don't access ifa_index when missing22Monitor
- ← EarlierCVE-2025-38029Jun 18, 2025 · kasan: avoid sleepable page allocation from atomic context22Monitor
- Later →CVE-2025-38041Jun 18, 2025 · clk: sunxi-ng: h616: Reparent GPU clock during frequency changes22Monitor
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 | 17e58be5b49f58bf17799a504f55c2d05ab2ecdc | Vendor (CNA) |
| Linux Linux | 3a982ada411b8c52695f1784c3f4784771f30209 | Vendor (CNA) |
| Linux Linux | 46d22b47df2741996af277a2838b95f130436c13 | Vendor (CNA) |
| Linux Linux | 6265538446e2426f4bf3b57e91d7680b2047ddd9 | Vendor (CNA) |
| Linux Linux | a21cb31642ffc84ca4ce55028212a96f72f54d30 | Vendor (CNA) |
| Linux Linux | c240375587ddcc80e1022f52ee32b946bbc3a639 | Vendor (CNA) |
| Linux Linux | ec462449f4cf616b0aa2ed119f5f44b5fdfcefab | Vendor (CNA) |
| Linux Linux | fc01b547c3f8bfa6e1d23cd5a2c63c736e8c3e4e | Vendor (CNA) |
| debian:linux | 6.1.147-1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-rt | 6.4.0-150600.10.49.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-rt_debug | 6.4.0-150600.10.49.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-source-rt | 6.4.0-150600.10.49.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-syms-rt | 6.4.0-150600.10.49.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:kernel-default | 6.4.0-32.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-default-base | 6.4.0-32.1.21.10 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-kvmsmall | 6.4.0-32.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6-RT_Update_14 | 1-150600.1.5.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-rt | 6.4.0-150600.10.49.1 · SUSE:Real Time Module 15 SP6 | Package registry (OSV) |
| suse:kernel-rt_debug | 6.4.0-150600.10.49.1 · SUSE:Real Time Module 15 SP6 | Package registry (OSV) |
| suse:kernel-source | 6.4.0-32.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-source-rt | 6.4.0-150600.10.49.1 · SUSE:Real Time Module 15 SP6 | Package registry (OSV) |
| suse:kernel-syms-rt | 6.4.0-150600.10.49.1 · SUSE:Real Time Module 15 SP6 | 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.
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 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
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 DereferenceCVSS 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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/3a982ada411b8c52695f1784c3f4784771f30209
- git.kernel.org/stable/c/46d22b47df2741996af277a2838b95f130436c13
- git.kernel.org/stable/c/6265538446e2426f4bf3b57e91d7680b2047ddd9
- git.kernel.org/stable/c/a21cb31642ffc84ca4ce55028212a96f72f54d30
- git.kernel.org/stable/c/c240375587ddcc80e1022f52ee32b946bbc3a639
- git.kernel.org/stable/c/ec462449f4cf616b0aa2ed119f5f44b5fdfcefab
- git.kernel.org/stable/c/fc01b547c3f8bfa6e1d23cd5a2c63c736e8c3e4e
- lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.