LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38617: net/packet: fix a race in packet_set_ring() and packet_notifier()

In the Linux kernel, the following vulnerability has been resolved: net/packet: fix a race in packet_set_ring() and packet_notifier() When packet_set_ring() releases po->bind_lock, another thread can run packet_notifier() and process an NETDEV_UP event. This race and the fix are both similar to that of commit 15fe076edea7 ("net/packet: fix a race in packet_bind() and packet_notifier()"). There too the packet_notifier NETDEV_UP event managed to run while a po->bind_lock critical section had to be temporarily released. And the fix was similarly to temporarily set po->num to zero to keep the socket unhooked until the lock is retaken. The po->bind_lock in packet_set_ring and packet_notifier precede the introduction of git history.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A race condition in Linux packet-socket handling may let a low-privileged local user compromise confidentiality, integrity, and availability. It is not remotely exploitable under the supplied CVSS vector, but multi-user systems, shared compute, and hosts running untrusted workloads warrant prompt assessment.

Executive priority

Treat this as a high-priority local privilege-boundary risk, especially on shared infrastructure. Patch exposed systems promptly through normal kernel maintenance, while ranking single-purpose hosts with tightly controlled local access below multi-tenant or untrusted-workload platforms. There is no supplied evidence requiring an emergency internet-wide response.

Technical view

The flaw occurs when packet_set_ring() temporarily releases po->bind_lock while packet_notifier() processes a NETDEV_UP event. The kernel fix temporarily sets po->num to zero, keeping the socket unhooked until the lock is reacquired. The supplied CVSS is 7.8: local access, low privileges, low complexity, no user interaction, and high potential impact.

Likely exposure

Exposure requires an affected Linux kernel and local low-privileged access to the vulnerable packet-socket behavior. Internet reachability alone does not establish exposure. The supplied version data is ambiguous and includes commit identifiers alongside release versions, so determine status using distribution advisories and backported-fix records rather than version-string comparison alone.

Exploitation context

The bundle references public exploitation research and a Google Security Research contribution, indicating practical security interest. However, CISA KEV status is false, and the supplied evidence does not establish active exploitation in the wild. Do not interpret public research as proof that production attacks are occurring.

Researcher notes

The vulnerable interleaving involves packet_set_ring() releasing bind_lock while packet_notifier() handles NETDEV_UP. The remediation mirrors an earlier packet_bind() race fix by clearing po->num during the unlocked interval. Exact affected-release boundaries and downstream backports cannot be reliably reconstructed from the bundle's version list; validate against stable commits and distributor advisories.

Mitigation direction

  • Install the vendor-supported kernel update containing the applicable stable fix or distribution backport.
  • Reboot into the updated kernel; installing packages alone may leave the vulnerable kernel running.
  • Prioritize shared, multi-user, container-hosting, and untrusted-workload systems where local access is more likely.
  • If immediate patching is impossible, consult vendor guidance for supported temporary mitigations; none are established in the bundle.

Validation and detection

  • Inventory running kernel versions, not only installed kernel packages, across Linux systems.
  • Map each kernel build to its distribution advisory and confirm whether the fix was backported.
  • Verify the running kernel changed after remediation and that vulnerable builds are no longer booted.
  • Review local-access and workload trust boundaries to identify systems where low-privileged users can reach packet-socket functionality.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-38617 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
14Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-38617Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2unaffected
LinuxLinux2.6.12, 0, 5.4.297, 5.10.241, 5.15.190, 6.1.148, 6.6.102, 6.12.42, 6.15.10, 6.16.1, 6.17affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.