Skip to content
vulneraibility.com
Screener

CVE-2026-46331

In the Linux kernel, the following vulnerability has been resolved: net/sched: fix pedit partial COW leading to page cache corruption tcf_pedit_act() computes the COW range for skb_ensure_writable() once before the key loop using tcfp_off_max_hint, but the hint does not account for the runtime header offset added by typed keys. This can leave part of the write region un-COW'd. Fix by moving skb_ensure_writable() inside the per-key loop where the actual write offset is known, and add overflow checking on the offset arithmetic. For negative offsets (e.g. Ethernet header edits at ingress), use skb_cow() to COW the headroom instead. Guard offset_valid() against INT_MIN, where negation is undefined.

CVSS
7.8Highscored by the publisher (CNA)
Exploited in the wild
Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
EPSS
0.64%chance of exploitation in the next 30 daystop 49% of scored CVEsFIRST score of 11 Nov 2026
Fix
Fixed in < 5.18, >= 5.10.260 and <= 5.10.*, >= 5.15.211 and <= 5.15.*per the vendor; 6 more listed below
Published
16 Jun 2026analysed here 12 Nov 2026

Do first. Upgrade to a fixed release: < 5.18, >= 5.10.260 and <= 5.10.*, >= 5.15.211 and <= 5.15.*, >= 6.1.177 and <= 6.1.* (and 5 more below).

Summary

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
local
Weaknesses
Can a WAF block it?
No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
Linux>= abe35bf3be51482593076d516a680d79e5fbc8e1 and < 544d857b42a1734b923040e13aa61a6fd4746cf2>= b773640d5bb9e2acfd91e2695717af04d47aa116 and < d5d01d35a5a7d36f7cb679b67d9cbdd5205672dc>= 8b796475fd7882663a870456466a4fb315cc1bd6 and < a071e057518decc5e3bec89855758f5f8786f2c5>= 8b796475fd7882663a870456466a4fb315cc1bd6 and < b685d6ef6f07a3b5ce814565a25f39f2157538a5>= 8b796475fd7882663a870456466a4fb315cc1bd6 and < 2bec122b9fb91507a758ab5e3e5c4fbe7cb3f61b>= 8b796475fd7882663a870456466a4fb315cc1bd6 and < b198ed4e52580a7238c7c7082f03906f8b310313>= 8b796475fd7882663a870456466a4fb315cc1bd6 and < 3dee9d0c198faeb95d052c1b94c2958751a28512>= 8b796475fd7882663a870456466a4fb315cc1bd6 and < 899ee91156e57784090c5565e4f31bd7dbffbc5ad0c38a914b0c4c21d553da801003d369790167262ec2dd7d51a9320151f275ddbb2b53260fb32ca1c19cc520b3d69904e9518d401ad0df7f4702aca0>= 5.10.117 and < 5.10.260>= 5.15.41 and < 5.15.211>= 4.19.244 and < 4.20>= 5.4.195 and < 5.5>= 5.17.9 and < 5.185.18Vendor says fixed in: < 5.18, >= 5.10.260 and <= 5.10.*, >= 5.15.211 and <= 5.15.*, >= 6.1.177 and <= 6.1.*, >= 6.6.144 and <= 6.6.*, >= 6.12.94 and <= 6.12.*, >= 6.18.36 and <= 6.18.*, >= 7.0.13 and <= 7.0.*, >= 7.1 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • linux:linux_kernel

Fix and mitigation

WAF and other mitigations

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: patch

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
Unvetted proof-of-concept code on GitHub: 14 GitHub proofs of concept
CISA SSVC
exploitation poc, automatable no, technical impact totalAssessed by CISA 29 Jun 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

GitHub proofs of concept

and 10 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 16 Jun 2026Published
  2. 17 Jun 2026First proof-of-concept repository on GitHub (unvetted)1 day later
  3. 29 Jun 2026CISA SSVC assessment: exploitation poc12 days later
  4. 15 Oct 2026CVE record last updated108 days (about 4 months) later
  5. 12 Nov 2026Analysed by vulneraibility.com28 days later

CVSS vector

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

MetricValueWhat it means
Attack vectorLocalLocal access required (shell, logged-in user).
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredLowThe attacker needs basic user privileges.
User interactionNoneNo victim action needed.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityHighComplete modification possible.
AvailabilityHighFull outage possible.

Common questions

Is CVE-2026-46331 being exploited?

Not confirmed. CVE-2026-46331 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.64% probability of exploitation in the next 30 days.

How severe is CVE-2026-46331?

CVE-2026-46331 is rated High with a CVSS score of 7.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-46331?

Yes. A fix has been recorded for CVE-2026-46331. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-46331 affect?

CVE-2026-46331 affects linux:linux_kernel. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

45 references in the CVE record, grouped by the tags the record gives them.

Advisories (32)

Show 26 more

Exploits (1)

Other links (12)

Show 6 more

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com