Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-40149: tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock().

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.17% (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 13159c7125636371543a82cb7bbae00ab36730cc, 2b1bef126bbb8d0da51491357559126d567c1dee, c65f27b9c3be2269918e1cbad6d8884741f835c5; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1; cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 5.15.200.1-1.

Low priority for now. Upgrade to Linux Linux 13159c7125636371543a82cb7bbae00ab36730cc, 2b1bef126bbb8d0da51491357559126d567c1dee, c65f27b9c3be2269918e1cbad6d8884741f835c5; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1; cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 5.15.200.1-1 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: tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock(). get_netdev_for_sock() is called during setsockopt(), so not under RCU. Using sk_dst_get(sk)->dev could trigger UAF. Let's use __sk_dst_get() and dst_dev_rcu(). Note that the only ->ndo_sk_get_lower_dev() user is bond_sk_get_lower_dev(), which uses RCU.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Nov 12, 2025
Updated
Oct 19, 2026
EPSS
0.1% · 6th 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
7.8
CNA · Linux
7.8
agree

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-2025-40149

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 kernel4.18 and later · before 5.15.199
  • linux linux kernel5.16 and later · before 6.1.161
  • linux linux kernel6.2 and later · before 6.6.121
  • linux linux kernel6.7 and later · before 6.12.66
  • linux linux kernel6.13 and later · before 6.17.3

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.18affected
    • e8f69799810c32dd40c6724d829eccc70baad07f and later · before 2b1bef126bbb8d0da51491357559126d567c1deeaffected · git
    • e8f69799810c32dd40c6724d829eccc70baad07f and later · before e37ca0092ddace60833790b4ad7a390408fb1be9affected · git
    • e8f69799810c32dd40c6724d829eccc70baad07f and later · before 13159c7125636371543a82cb7bbae00ab36730ccaffected · git
    • e8f69799810c32dd40c6724d829eccc70baad07f and later · before f09cd209359a23f88d4f3fa3d2379d057027e53caffected · git
    • e8f69799810c32dd40c6724d829eccc70baad07f and later · before feb474ddbf26b51f462ae2e60a12013bdcfc5407affected · git
    • e8f69799810c32dd40c6724d829eccc70baad07f and later · before c65f27b9c3be2269918e1cbad6d8884741f835c5affected · git
    • before 4.18not affected · semver
    • 5.15.199 and later · up to and including 5.15.*not affected · semver
    • 6.1.161 and later · up to and including 6.1.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.55.1.el10_26.12.0-211.55.1.el10_2

+96

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-2025-40082Oct 28, 2025 · hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()
    28Monitor
  • ← EarlierCVE-2025-40090Oct 30, 2025 · ksmbd: fix recursive locking in RPC handle list access
    22Monitor
  • Later →CVE-2025-40164Nov 12, 2025 · usbnet: Fix using smp_processor_id() in preemptible code warnings
    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 Linux13159c7125636371543a82cb7bbae00ab36730ccVendor (CNA)
Linux Linux2b1bef126bbb8d0da51491357559126d567c1deeVendor (CNA)
Linux Linuxc65f27b9c3be2269918e1cbad6d8884741f835c5Vendor (CNA)
Linux Linuxe37ca0092ddace60833790b4ad7a390408fb1be9Vendor (CNA)
Linux Linuxf09cd209359a23f88d4f3fa3d2379d057027e53cVendor (CNA)
Linux Linuxfeb474ddbf26b51f462ae2e60a12013bdcfc5407Vendor (CNA)
azl3 kernel 6.6.119.3-3 on Azure Linux 3.06.6.121.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.05.15.200.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel6.12.0-211.55.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.55.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.55.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.55.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.55.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.55.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.55.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.55.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.55.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.55.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.55.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.55.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-55.103.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-55.103.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-55.103.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-55.103.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-55.103.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-55.103.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-55.103.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-55.103.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-55.103.1.el10_0 · Red Hat:enterprise_linux_eus:10.0Package registry (OSV)

+4

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

  • 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-primary

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