Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-53260: tcp: Add preempt_{disable,enable}_nested() in reqsk_queue_hash_req().

Noroxi assessment

Priority: Monitor (action score 39/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.29% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. 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 889fc99967007e2493833515a645cb2d800f6742, b183215ff714efb747d9d5a429322ba6404b5401, de5a46f3b2c8d3cd20afa158bd3a725e3e3d6fd3.

Low priority for now. Upgrade to Linux Linux 889fc99967007e2493833515a645cb2d800f6742, b183215ff714efb747d9d5a429322ba6404b5401, de5a46f3b2c8d3cd20afa158bd3a725e3e3d6fd3 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: tcp: Add preempt_{disable,enable}_nested() in reqsk_queue_hash_req(). syzbot reported a weird reqsk->rsk_refcnt underflow in __inet_csk_reqsk_queue_drop(). The captured reqsk_put() in __inet_csk_reqsk_queue_drop() is called only when it successfully removes reqsk from ehash. Moreover, reqsk_timer_handler() calls another reqsk_put() after that. This indicates that the reqsk was missing both refcnts for ehash and the timer itself. Since all the syzbot reports had PREEMPT_RT enabled, the only possible scenario is that reqsk_queue_hash_req() is preempted after mod_timer() and before refcount_set(), and then the timer triggered after 1s aborts the reqsk due to its listener's close(). Let's wrap mod_timer() and refcount_set() with preempt_disable_nested() and preempt_enable_nested(). Note that inet_ehash_insert() holds the normal spin_lock() (mutex in PREEMPT_RT), so it must be called outside of preempt_disable_nested(), but this is fine. The lookup path just ignores 0 sk_refcnt entries in ehash and tries to create another reqsk, but this will fail at inet_ehash_insert(). [0]: refcount_t: underflow; use-after-free. WARNING: lib/refcount.c:28 at refcount_warn_saturate+0xb2/0x110 lib/refcount.c:28, CPU#0: ktimers/0/16 Modules linked in: CPU: 0 UID: 0 PID: 16 Comm: ktimers/0 Tainted: G L syzkaller #0 PREEMPT_{RT,(full)} Tainted: [L]=SOFTLOCKUP Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026 RIP: 0010:refcount_warn_saturate+0xb2/0x110 lib/refcount.c:28 Code: e4 7d d1 0a 67 48 0f b9 3a eb 4a e8 38 3d 23 fd 48 8d 3d e1 7d d1 0a 67 48 0f b9 3a eb 37 e8 25 3d 23 fd 48 8d 3d de 7d d1 0a <67> 48 0f b9 3a eb 24 e8 12 3d 23 fd 48 8d 3d db 7d d1 0a 67 48 0f RSP: 0000:ffffc90000157948 EFLAGS: 00010246 RAX: ffffffff84a1301b RBX: 0000000000000003 RCX: ffff88801ca98000 RDX: 0000000000000100 RSI: 0000000000000000 RDI: ffffffff8f72ae00 RBP: ffffffff99ae3b01 R08: ffff88801ca98000 R09: 0000000000000005 R10: 0000000000000100 R11: 0000000000000004 R12: ffff8880425ef568 R13: ffff8880425ef4f8 R14: ffff8880425ef578 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff888126386000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f7b46710e9c CR3: 000000000dbb6000 CR4: 00000000003526f0 Call Trace: <TASK> __refcount_sub_and_test include/linux/refcount.h:400 [inline] __refcount_dec_and_test include/linux/refcount.h:432 [inline] refcount_dec_and_test include/linux/refcount.h:450 [inline] reqsk_put include/net/request_sock.h:136 [inline] __inet_csk_reqsk_queue_drop+0x3ce/0x440 net/ipv4/inet_connection_sock.c:1007 reqsk_timer_handler+0x651/0xdf0 net/ipv4/inet_connection_sock.c:1137 call_timer_fn+0x192/0x5e0 kernel/time/timer.c:1748 expire_timers kernel/time/timer.c:1799 [inline] __run_timers kernel/time/timer.c:2374 [inline] __run_timer_base+0x6a3/0x9f0 kernel/time/timer.c:2386 run_timer_base kernel/time/timer.c:2395 [inline] run_timer_softirq+0x67/0x170 kernel/time/timer.c:2403 handle_softirqs+0x1de/0x6d0 kernel/softirq.c:622 __do_softirq kernel/softirq.c:656 [inline] run_ktimerd+0x69/0x100 kernel/softirq.c:1151 smpboot_thread_fn+0x541/0xa50 kernel/smpboot.c:160 kthread+0x388/0x470 kernel/kthread.c:436 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 </TASK>

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Jun 25, 2026
Updated
Oct 19, 2026
EPSS
0.2% · 22th percentile

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
9.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-2026-53260

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.

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

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.12 and later · before 7.0.13
  • linux linux kernel7.1

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

    • 6.12affected
    • d2d6422f8bd17c6bb205133e290625a564194496 and later · before 889fc99967007e2493833515a645cb2d800f6742affected · git
    • d2d6422f8bd17c6bb205133e290625a564194496 and later · before de5a46f3b2c8d3cd20afa158bd3a725e3e3d6fd3affected · git
    • d2d6422f8bd17c6bb205133e290625a564194496 and later · before b183215ff714efb747d9d5a429322ba6404b5401affected · git
    • d2d6422f8bd17c6bb205133e290625a564194496 and later · before e10902df24488ca722303133acfc82490f7d59adaffected · git
    • before 6.12not affected · semver
    • 6.12.97 and later · up to and including 6.12.*not affected · semver
    • 6.18.40 and later · up to and including 6.18.*not affected · semver
    • 7.0.13 and later · up to and including 7.0.*not affected · semver
    • 7.1 and laternot affected · original_commit_for_fix

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linux-6.12before 6.12.100-1~deb12u16.12.100-1~deb12u1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.0.13-17.0.13-1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-64kbbefore 5.14.21-150400.24.240.25.14.21-150400.24.240.2
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-docsbefore 5.14.21-150400.24.240.15.14.21-150400.24.240.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-obs-buildbefore 5.14.21-150400.24.240.15.14.21-150400.24.240.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-symsbefore 5.14.21-150400.24.240.15.14.21-150400.24.240.1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSkernel-64kbbefore 5.14.21-150500.55.189.15.14.21-150500.55.189.1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSkernel-docsbefore 5.14.21-150500.55.189.15.14.21-150500.55.189.1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSkernel-obs-buildbefore 5.14.21-150500.55.189.15.14.21-150500.55.189.1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSkernel-symsbefore 5.14.21-150500.55.189.15.14.21-150500.55.189.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_59before 1-150400.9.5.11-150400.9.5.1
SUSE:Linux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_45before 1-150500.11.5.31-150500.11.5.3
SUSE:Linux Enterprise Micro 5.3kernel-defaultbefore 5.14.21-150400.24.240.25.14.21-150400.24.240.2
SUSE:Linux Enterprise Micro 5.3kernel-default-basebefore 5.14.21-150400.24.240.2.150400.24.120.25.14.21-150400.24.240.2.150400.24.120.2
SUSE:Linux Enterprise Micro 5.3kernel-rtbefore 5.14.21-150400.15.186.15.14.21-150400.15.186.1
SUSE:Linux Enterprise Micro 5.3kernel-sourcebefore 5.14.21-150400.24.240.15.14.21-150400.24.240.1
SUSE:Linux Enterprise Micro 5.3kernel-source-rtbefore 5.14.21-150400.15.186.15.14.21-150400.15.186.1
SUSE:Linux Enterprise Micro 5.5kernel-defaultbefore 5.14.21-150500.55.189.15.14.21-150500.55.189.1
SUSE:Linux Enterprise Micro 5.5kernel-default-basebefore 5.14.21-150500.55.189.1.150500.6.87.45.14.21-150500.55.189.1.150500.6.87.4
SUSE:Linux Enterprise Micro 5.5kernel-rtbefore 5.14.21-150500.13.161.15.14.21-150500.13.161.1
SUSE:Linux Enterprise Micro 5.5kernel-sourcebefore 5.14.21-150500.55.189.15.14.21-150500.55.189.1
SUSE:Linux Enterprise Micro 5.5kernel-source-rtbefore 5.14.21-150500.13.161.15.14.21-150500.13.161.1
SUSE:Linux Enterprise Server 15 SP4-LTSSkernel-zfcpdumpbefore 5.14.21-150400.24.240.25.14.21-150400.24.240.2

+1

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-2026-53257Jun 25, 2026 · wifi: cfg80211: enforce HE/EHT cap/oper consistency
    22Monitor
  • ← EarlierCVE-2026-53258Jun 25, 2026 · wifi: fix leak if split 6 GHz scanning fails
    22Monitor
  • Later →CVE-2026-53261Jun 25, 2026 · devlink: Release nested relation on devlink free
    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 Linux889fc99967007e2493833515a645cb2d800f6742Vendor (CNA)
Linux Linuxb183215ff714efb747d9d5a429322ba6404b5401Vendor (CNA)
Linux Linuxde5a46f3b2c8d3cd20afa158bd3a725e3e3d6fd3Vendor (CNA)
Linux Linuxe10902df24488ca722303133acfc82490f7d59adVendor (CNA)
debian:linux6.12.100-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.100-1~deb12u1 · Debian:12Package registry (OSV)
suse:kernel-64kb5.14.21-150400.24.240.2 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSPackage registry (OSV)
suse:kernel-default5.14.21-150400.24.240.2 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:kernel-default-base5.14.21-150400.24.240.2.150400.24.120.2 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:kernel-docs5.14.21-150400.24.240.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSPackage registry (OSV)
suse:kernel-livepatch-SLE15-SP4_Update_591-150400.9.5.1 · SUSE:Linux Enterprise Live Patching 15 SP4Package registry (OSV)
suse:kernel-livepatch-SLE15-SP5_Update_451-150500.11.5.3 · SUSE:Linux Enterprise Live Patching 15 SP5Package registry (OSV)
suse:kernel-obs-build5.14.21-150400.24.240.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSPackage registry (OSV)
suse:kernel-rt5.14.21-150400.15.186.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:kernel-source5.14.21-150400.24.240.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:kernel-source-rt5.14.21-150400.15.186.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:kernel-syms5.14.21-150400.24.240.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSPackage registry (OSV)
suse:kernel-zfcpdump5.14.21-150400.24.240.2 · SUSE:Linux Enterprise Server 15 SP4-LTSSPackage 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.

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

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • 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
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records