Skip to content
Noroxi
CVE-2026-68290· NVD / CVE Program· CNA Linux

rds: tcp: unregister sysctl before tearing down listen socket

Noroxi assessment

Priority: Monitor (action score 31/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.12% (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 167e54c703ccd4fa028feb568b0d1002020cff86, 16df2d154ec82e2f7e7585b4fa154751ba37729a, 3aa13fe0c1bb7bc5312f878e61523e5d8cf3f85d.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 167e54c703ccd4fa028feb568b0d1002020cff86, 16df2d154ec82e2f7e7585b4fa154751ba37729a, 3aa13fe0c1bb7bc5312f878e61523e5d8cf3f85d 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: rds: tcp: unregister sysctl before tearing down listen socket rds_tcp_exit_net() frees the per-netns RDS TCP listen socket via rds_tcp_kill_sock() before unregistering the per-netns sysctl table. Since rds_tcp_skbuf_handler() derives the netns from rtn->rds_tcp_listen_sock->sk, a concurrent sysctl write can race with netns teardown and dereference the freed socket/sk. KASAN reports the race as: BUG: KASAN: slab-use-after-free in rds_tcp_skbuf_handler+0x2aa/0x2e0 rds_tcp_skbuf_handler net/rds/tcp.c:721 proc_sys_call_handler fs/proc/proc_sysctl.c vfs_write fs/read_write.c __x64_sys_pwrite64 fs/read_write.c Fix this by unregistering the RDS TCP sysctl table before calling rds_tcp_kill_sock(). unregister_net_sysctl_table() prevents new sysctl handlers from starting and waits for in-flight handlers to finish, so the listen socket can then be released safely. The fix was tested against the linked reproducer.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Aug 10, 2026
Updated
Oct 21, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.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-68290

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.

—

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

    • 33b3e09a489a31b30342b77cc55290f025d95c7e, 6.13affected
    • de8d6de0ee27be4b2b1e5b06f04aeacbabbba492 and later · before 80fffed08dc1c10e971066941d2daa56253f1552affected · git
    • 7f5611cbc4871c7fb1ad36c2e5a9edad63dca95c and later · before 16df2d154ec82e2f7e7585b4fa154751ba37729aaffected · git
    • 7f5611cbc4871c7fb1ad36c2e5a9edad63dca95c and later · before 3aa13fe0c1bb7bc5312f878e61523e5d8cf3f85daffected · git
    • 7f5611cbc4871c7fb1ad36c2e5a9edad63dca95c and later · before 167e54c703ccd4fa028feb568b0d1002020cff86affected · git
    • 6.12.10 and later · before 6.12.101affected · semver
    • 6.6.160 and later · before 6.7affected · semver
    • before 6.13not affected · semver
    • 6.12.101 and later · up to and including 6.12.*not affected · semver
    • 6.18.42 and later · up to and including 6.18.*not affected · semver

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.101-1~deb12u16.12.101-1~deb12u1
Debian:13linuxbefore 6.12.101-16.12.101-1
Debian:14linuxbefore 7.1.6-17.1.6-1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-defaultbefore 6.4.0-150600.23.138.16.4.0-150600.23.138.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_32before 1-150600.13.3.11-150600.13.3.1
SUSE:Linux Enterprise Server 15 SP6-LTSSkernel-64kbbefore 6.4.0-150600.23.138.16.4.0-150600.23.138.1
SUSE:Linux Enterprise Server 15 SP6-LTSSkernel-default-basebefore 6.4.0-150600.23.138.1.150600.12.64.16.4.0-150600.23.138.1.150600.12.64.1
SUSE:Linux Enterprise Server 15 SP6-LTSSkernel-docsbefore 6.4.0-150600.23.138.16.4.0-150600.23.138.1
SUSE:Linux Enterprise Server 15 SP6-LTSSkernel-obs-buildbefore 6.4.0-150600.23.138.16.4.0-150600.23.138.1
SUSE:Linux Enterprise Server 15 SP6-LTSSkernel-sourcebefore 6.4.0-150600.23.138.16.4.0-150600.23.138.1
SUSE:Linux Enterprise Server 15 SP6-LTSSkernel-symsbefore 6.4.0-150600.23.138.16.4.0-150600.23.138.1
SUSE:Linux Enterprise Server 15 SP6-LTSSkernel-zfcpdumpbefore 6.4.0-150600.23.138.16.4.0-150600.23.138.1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-68288Aug 10, 2026 · net: drop_monitor: fix info leak in NET_DM_ATTR_PAYLOAD
    0Monitor
  • ← EarlierCVE-2026-68289Aug 10, 2026 · tipc: fix integer overflow in tipc_recvmsg() and tipc_recvstream()
    0Monitor
  • Later →CVE-2026-68291Aug 10, 2026 · idpf: fix max_vport related crash on allocation error during init
    0Monitor

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 Linux167e54c703ccd4fa028feb568b0d1002020cff86Vendor (CNA)
Linux Linux16df2d154ec82e2f7e7585b4fa154751ba37729aVendor (CNA)
Linux Linux3aa13fe0c1bb7bc5312f878e61523e5d8cf3f85dVendor (CNA)
Linux Linux6.12.101Vendor (CNA)
Linux Linux6.7Vendor (CNA)
Linux Linux80fffed08dc1c10e971066941d2daa56253f1552Vendor (CNA)
debian:linux6.12.101-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.101-1~deb12u1 · Debian:12Package registry (OSV)
suse:kernel-64kb6.4.0-150600.23.138.1 · SUSE:Linux Enterprise Server 15 SP6-LTSSPackage registry (OSV)
suse:kernel-default6.4.0-150600.23.138.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-default-base6.4.0-150600.23.138.1.150600.12.64.1 · SUSE:Linux Enterprise Server 15 SP6-LTSSPackage registry (OSV)
suse:kernel-docs6.4.0-150600.23.138.1 · SUSE:Linux Enterprise Server 15 SP6-LTSSPackage registry (OSV)
suse:kernel-livepatch-SLE15-SP6_Update_321-150600.13.3.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-obs-build6.4.0-150600.23.138.1 · SUSE:Linux Enterprise Server 15 SP6-LTSSPackage registry (OSV)
suse:kernel-source6.4.0-150600.23.138.1 · SUSE:Linux Enterprise Server 15 SP6-LTSSPackage registry (OSV)
suse:kernel-syms6.4.0-150600.23.138.1 · SUSE:Linux Enterprise Server 15 SP6-LTSSPackage registry (OSV)
suse:kernel-zfcpdump6.4.0-150600.23.138.1 · SUSE:Linux Enterprise Server 15 SP6-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.

EPSS, last 120 days

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.

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.

  • CVE-2026-681170 days aparttipc: clear sock->sk on the failed-insert path in tipc_sk_create()
    39Monitor
  • CVE-2026-681270 days apartila: reload IPv6 header after pskb_may_pull in checksum adjust
    39Monitor
  • CVE-2026-681440 days apartphonet: pep: fix use-after-free in pep_get_sb()
    39Monitor
  • CVE-2026-681560 days apartlibceph: refresh auth->authorizer_buf{,_len} after authorizer update
    39Monitor
  • CVE-2026-683810 days apartksmbd: pin conn during async oplock break notification
    39Monitor
  • CVE-2026-684260 days apartxfrm: fix stale skb->prev after async crypto steals a GSO segment
    39Monitor

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
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:L/AC:L/PR:L/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