dbcve.org
Linux KernelOperating system · Linux

CVE-2026-23245

HIGH · 7.8 CVSS v3.1 Published 2026-03-18
Fix available
A fix is available. Upgrade to 5.10.253 / 6.1.167 or later.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: net/sched: act_gate: snapshot parameters with RCU on replace The gate action can be replaced while the hrtimer callback or dump path is walking the schedule list. Convert the parameters to an RCU-protected snapshot and swap updates under tcf_lock, freeing the previous snapshot via call_rcu(). When REPLACE omits the entry list, preserve the existing schedule so the effective state is unchanged.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 5.8.1, < 5.10.253>= 5.11, < 6.1.167>= 6.2, < 6.6.130>= 6.7, < 6.12.78>= 6.13, < 6.18.18>= 6.19, < 6.19.8= 5.8= 7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.10.253 / 6.1.167 / 6.6.130 or later
Fixed in 5.10.2536.1.1676.6.130
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to kernel 5.10.253+, 6.1.167+, 6.6.130+, or 6.12.78+ depending on which branch is in use

  1. Identify the current Linux kernel version using 'uname -r'
  2. Determine which kernel branch is in use (e.g., 5.10.x, 6.1.x, 6.2.x, 6.7.x, 6.12.x)
  3. For Debian/Ubuntu: Run 'sudo apt update && sudo apt upgrade' or install a newer kernel package
  4. For RHEL/CentOS: Run 'sudo yum update' or 'sudo dnf update' to get the latest kernel
  5. For other distributions: Update using the distribution's standard package manager
  6. Reboot the system to load the new kernel
  7. Verify the kernel version after reboot with 'uname -r' to confirm the fix is applied
Caveat Kernel upgrades may require system reboot and could have compatibility issues with custom modules or specific hardware drivers; test in staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-23245 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-23245 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data