BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-74478High confidence

um: vector: fix use-after-free in vector_mmsg_rx()

Linux · Linux

9.8CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.86% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

25 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.105-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.187-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.107-1~deb12u1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-74478 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: um: vector: fix use-after-free in vector_mmsg_rx()
274 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel. A remote attacker, by sending specially crafted packets over GRE or L2TPv3 transports, could trigger a use-after-free vulnerability. This occurs in the `vector_mmsg_rx()` function when a packet's overlay header fails verification, causing the system to attempt to free an already freed network buffer. This issue leads to a denial of service.
Remediation
No remediation text is recorded.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-59671

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: um: vector: fix use-after-free in vector_mmsg_rx() When vector_mmsg_rx() discards a packet whose overlay header fails verify_header(), it frees the skb and continues the loop: if (header_check < 0) { dev_kfree_skb_irq(skb); vp->estats.rx_encaps_errors++; continue; } The normal and short-packet paths fall through to the bottom of the loop body, which clears the consumed slot and advances the cursors: (*skbuff_vector) = NULL; mmsg_vector++; skbuff_vector++; The verify_header() < 0 path skips that via continue, so the freed skb is left in skbuff_vector[] and the cursors do not advance. The next iteration reads the same slot, gets the freed skb, and frees it again, producing a refcount underflow / use-after-free in the RX path. Discard the slot the same way the other paths do before continuing. Only transports whose verify_header() can return negative are affected: GRE and L2TPv3 do so on a cookie/session-id mismatch (raw/tap do not), so any peer on such a transport can trigger it without authentication.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
9.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: um: vector: fix use-after-free in vector_mmsg_rx() When vector_mmsg_rx() discards a packet whose overlay header fails verify_header(), it frees the skb and continues the loop: if (header_check < 0) { dev_kfree_skb_irq(skb); vp->estats.rx_encaps_errors++; continue; } The normal and short-packet paths fall through to the bottom of the loop body, which clears the consumed slot and advances the cursors: (*skbuff_vector) = NULL; mmsg_vector++; skbuff_vector++; The verify_header() < 0 path skips that via continue, so the freed skb is left in skbuff_vector[] and the cursors do not advance. The next iteration reads the same slot, gets the freed skb, and frees it again, producing a refcount underflow / use-after-free in the RX path. Discard the slot the same way the other paths do before continuing. Only transports whose verify_header() can return negative are affected: GRE and L2TPv3 do so on a cookie/session-id mismatch (raw/tap do not), so any peer on such a transport can trigger it without authentication.

What

In the Linux kernel, the following vulnerability has been resolved: um: vector: fix use-after-free in vector_mmsg_rx() When vector_mmsg_rx() discards a packet whose overlay header fails verify_header(), it frees the skb and continues the loop: if (header_check < 0) { dev_kfree_skb_irq(skb); vp->estats.rx_encaps_errors++; continue; } The normal and short-packet paths fall through to the bottom of the loop body, which clears the consumed slot and advances the cursors: (*skbuff_vector) = NULL; mmsg_vector++; skbuff_vector++; The verify_header() < 0 path skips that via continue, so the freed skb is left in skbuff_vector[] and the cursors do not advance. The next iteration reads the same slot, gets the freed skb, and frees it again, producing a refcount underflow / use-after-free in the RX path. Discard the slot the same way the other paths do before continuing. Only transports whose verify_header() can return negative are affected: GRE and L2TPv3 do so on a cookie/session-id mismatch (raw/tap do not), so any peer on such a transport can trigger it without authentication.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: um: vector: fix use-after-free in vector_mmsg_rx() When vector_mmsg_rx() discards a packet whose overlay header fails verify_header(), it frees the skb and continues the loop: if (header_check < 0) { dev_kfree_skb_irq(skb); vp->estats.rx_encaps_errors++; continue; } The normal and short-packet paths fall through to the bottom of the loop body, which clears the consumed slot and advances the cursors: (*skbuff_vector) = NULL; mmsg_vector++; skbuff_vector++; The verify_header() < 0 path skips that via continue, so the freed skb is left in skbuff_vector[] and the cursors do not advance. The next iteration reads the same slot, gets the freed skb, and frees it again, producing a refcount underflow / use-after-free in the RX path. Discard the slot the same way the other paths do before continuing. Only transports whose verify_header() can return negative are affected: GRE and L2TPv3 do so on a cookie/session-id mismatch (raw/tap do not), so any peer on such a transport can trigger it without authentication.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticated
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-59671Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: um: vector: fix use-after-free in vector_mmsg_rx() When vector_mmsg_rx() discards a packet whose overlay header fails verify_header(), it frees the skb and continues the loop: if (header_check < 0) { dev_kfree_skb_irq(skb); vp->estats.rx_encaps_errors++; continue; } The normal and short-packet paths fall through to the bottom of the loop body, which clears the consumed slot and advances the cursors: (*skbuff_vector) = NULL; mmsg_vector++; skbuff_vector++; The verify_header() < 0 path skips that via continue, so the freed skb is left in skbuff_vector[] and the cursors do not advance. The next iteration reads the same slot, gets the freed skb, and frees it again, producing a refcount underflow / use-after-free in the RX path. Discard the slot the same way the other paths do before continuing. Only transports whose verify_header() can return negative are affected: GRE and L2TPv3 do so on a cookie/session-id mismatch (raw/tap do not), so any peer on such a transport can trigger it without authentication.

Official EUVD record ↗
BSI · German · WID-SEC-2026-2852Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1232Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-74468 Référence CVE CVE-2026-74469 https://www.cve.org/CVERecord?id=CVE-2026-74469 Référence CVE CVE-2026-74470 https://www.cve.org/CVERecord?id=CVE-2026-74470 Référence CVE CVE-2026-74471 https://www.cve.org/CVERecord?id=CVE-2026-74471 Référence CVE CVE-2026-74472 https://www.cve.org/CVERecord?id=CVE-2026-74472 Référence CVE CVE-2026-74473 https://www.cve.org/CVERecord?id=CVE-2026-74473 Référence CVE CVE-2026-74474 https://www.cve.org/CVERecord?id=CVE-2026-74474 Référence CVE CVE-2026-74475 https://www.cve.org/CVERecord?id=CVE-2026-74475 Référence CVE CVE-2026-74476 https://www.cve.org/CVERecord?id=CVE-2026-74476 Référence CVE CVE-2026-74478 https://www.cve.org/CVERecord?id=CVE-2026-74478 Référence CVE CVE-2026-74479 https://www.cve.org/CVERecord?id=CVE-2026-74479 Référence CVE CVE-2026-74480 https://www.cve.org/CVERecord?id=CVE-2026-74480 Référence CVE CVE-2026-74481 https://www.cve.org/CVERecord?id=CVE-2026-74481 Référence CVE CVE-2026-74482 https://www.cve.org/CVERecord?id=CVE-2026-74482 Référence CVE CVE-2026-74483 https://www.cve.org/CVERecord?id=CVE-2026-74483 Référence CVE CVE-2026-74484 https://www.cve.org/CVERecord?id=CVE-2026-74484 Référence CVE CVE-2026-74485 https://www.cve.org/CVERecord?id=CVE-2026-74485 Référence CVE CVE-2026-74487 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1203Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-74417 Référence CVE CVE-2026-74427 https://www.cve.org/CVERecord?id=CVE-2026-74427 Référence CVE CVE-2026-74436 https://www.cve.org/CVERecord?id=CVE-2026-74436 Référence CVE CVE-2026-74439 https://www.cve.org/CVERecord?id=CVE-2026-74439 Référence CVE CVE-2026-74440 https://www.cve.org/CVERecord?id=CVE-2026-74440 Référence CVE CVE-2026-74473 https://www.cve.org/CVERecord?id=CVE-2026-74473 Référence CVE CVE-2026-74474 https://www.cve.org/CVERecord?id=CVE-2026-74474 Référence CVE CVE-2026-74475 https://www.cve.org/CVERecord?id=CVE-2026-74475 Référence CVE CVE-2026-74476 https://www.cve.org/CVERecord?id=CVE-2026-74476 Référence CVE CVE-2026-74478 https://www.cve.org/CVERecord?id=CVE-2026-74478 Référence CVE CVE-2026-74480 https://www.cve.org/CVERecord?id=CVE-2026-74480 Référence CVE CVE-2026-74493 https://www.cve.org/CVERecord?id=CVE-2026-74493 Référence CVE CVE-2026-74495 https://www.cve.org/CVERecord?id=CVE-2026-74495 Référence CVE CVE-2026-74521 https://www.cve.org/CVERecord?id=CVE-2026-74521 Référence CVE CVE-2026-74538 https://www.cve.org/CVERecord?id=CVE-2026-74538 Référence CVE CVE-2026-74541 https://www.cve.org/CVERecord?id=CVE-2026-74541 Référence CVE CVE-2026-74556 https://www.cve.org/CVERecord?id=CVE-2026-74556 Référence CVE CVE-2026-74569 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1163Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-74467 Référence CVE CVE-2026-74468 https://www.cve.org/CVERecord?id=CVE-2026-74468 Référence CVE CVE-2026-74469 https://www.cve.org/CVERecord?id=CVE-2026-74469 Référence CVE CVE-2026-74470 https://www.cve.org/CVERecord?id=CVE-2026-74470 Référence CVE CVE-2026-74471 https://www.cve.org/CVERecord?id=CVE-2026-74471 Référence CVE CVE-2026-74472 https://www.cve.org/CVERecord?id=CVE-2026-74472 Référence CVE CVE-2026-74473 https://www.cve.org/CVERecord?id=CVE-2026-74473 Référence CVE CVE-2026-74475 https://www.cve.org/CVERecord?id=CVE-2026-74475 Référence CVE CVE-2026-74476 https://www.cve.org/CVERecord?id=CVE-2026-74476 Référence CVE CVE-2026-74478 https://www.cve.org/CVERecord?id=CVE-2026-74478 Référence CVE CVE-2026-74479 https://www.cve.org/CVERecord?id=CVE-2026-74479 Référence CVE CVE-2026-74480 https://www.cve.org/CVERecord?id=CVE-2026-74480 Référence CVE CVE-2026-74481 https://www.cve.org/CVERecord?id=CVE-2026-74481 Référence CVE CVE-2026-74482 https://www.cve.org/CVERecord?id=CVE-2026-74482 Référence CVE CVE-2026-74485 https://www.cve.org/CVERecord?id=CVE-2026-74485 Référence CVE CVE-2026-74487 https://www.cve.org/CVERecord?id=CVE-2026-74487 Référence CVE CVE-2026-74488 https://www.cve.org/CVERecord?id=CVE-2026-74488 Référence CVE CVE-2026-74490 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1090Multiples vulnérabilités dans le noyau Linux de Debian

d?id=CVE-2026-74468 Référence CVE CVE-2026-74469 https://www.cve.org/CVERecord?id=CVE-2026-74469 Référence CVE CVE-2026-74470 https://www.cve.org/CVERecord?id=CVE-2026-74470 Référence CVE CVE-2026-74471 https://www.cve.org/CVERecord?id=CVE-2026-74471 Référence CVE CVE-2026-74472 https://www.cve.org/CVERecord?id=CVE-2026-74472 Référence CVE CVE-2026-74473 https://www.cve.org/CVERecord?id=CVE-2026-74473 Référence CVE CVE-2026-74474 https://www.cve.org/CVERecord?id=CVE-2026-74474 Référence CVE CVE-2026-74475 https://www.cve.org/CVERecord?id=CVE-2026-74475 Référence CVE CVE-2026-74476 https://www.cve.org/CVERecord?id=CVE-2026-74476 Référence CVE CVE-2026-74478 https://www.cve.org/CVERecord?id=CVE-2026-74478 Référence CVE CVE-2026-74479 https://www.cve.org/CVERecord?id=CVE-2026-74479 Référence CVE CVE-2026-74480 https://www.cve.org/CVERecord?id=CVE-2026-74480 Référence CVE CVE-2026-74481 https://www.cve.org/CVERecord?id=CVE-2026-74481 Référence CVE CVE-2026-74482 https://www.cve.org/CVERecord?id=CVE-2026-74482 Référence CVE CVE-2026-74483 https://www.cve.org/CVERecord?id=CVE-2026-74483 Référence CVE CVE-2026-74484 https://www.cve.org/CVERecord?id=CVE-2026-74484 Référence CVE CVE-2026-74485 https://www.cve.org/CVERecord?id=CVE-2026-74485 Référence CVE CVE-2026-74487 https://www.cve.org/CVERecord?id=

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Linux: 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 967c779c9853d2a1cc9cd8e61d300250c348f3d9, 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < a7bc015bb798c525e7a82dd14225c6aeb994274b, 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 7dc9781e320d664c9bdd50003c9acfddf363d1e1, 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 4b9601595e8b6b5d18878cac0aeabc687d241111, 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 67d58ab4f2ccf7145f3da07e025735a09c79de1b, 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 180ff4c81faf01ec4e06082c9daa7c40518ead89, 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 804b681002ead233abf49a3efd681f5468a835f9, 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < af421e9aed3920c7ac88c24daa48606c7112feca, 4.17
Fixed
Linux: < 4.17, 5.10.265 ≤ 5.10.*, 5.15.216 ≤ 5.15.*, 6.1.183 ≤ 6.1.*, 6.6.151 ≤ 6.6.*, 6.12.103 ≤ 6.12.*, 6.18.44 ≤ 6.18.*, 7.1.8 ≤ 7.1.*, 7.2 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 15 Aug 2026 · Last source change 19 Aug 2026, 16:37 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-23
European sourceENISA EUVD · EUVD-2026-59671
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD received

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/967c779c9853d2a1cc9cd8e61d300250c348f3d9; removed remediation: git.kernel.org/4b9601595e8b6b5d18878cac0aeabc687d241111.
    Before
    remediation: git.kernel.org/4b9601595e8b6b5d18878cac0aeabc687d241111
    After
    remediation: git.kernel.org/967c779c9853d2a1cc9cd8e61d300250c348f3d9
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 4b9601595e8b6b5d18878cac0aeabc687d241111; 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 67d58ab4f2ccf7145f3da07e025735a09c79de1b; 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 180ff4c81faf01ec4e06082c9daa7c40518ead89; 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 804b681002ead233abf49a3efd681f5468a835f9; 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < af421e9aed3920c7ac88c24daa48606c7112feca; 4.17 · Fixed: < 4.17; 6.6.151 ≤ 6.6.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2 ≤ *
    After
    49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 967c779c9853d2a1cc9cd8e61d300250c348f3d9; 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < a7bc015bb798c525e7a82dd14225c6aeb994274b; 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 7dc9781e320d664c9bdd50003c9acfddf363d1e1; 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 4b9601595e8b6b5d18878cac0aeabc687d241111; 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 67d58ab4f2ccf7145f3da07e025735a09c79de1b; 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 180ff4c81faf01ec4e06082c9daa7c40518ead89; 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 804b681002ead233abf49a3efd681f5468a835f9; 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < af421e9aed3920c7ac88c24daa48606c7112feca · Fixed: < 4.17; 5.10.265 ≤ 5.10.*; 5.15.216 ≤ 5.15.*; 6.1.183 ≤ 6.1.*; 6.6.151 ≤ 6.6.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*
    CNA ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 4b9601595e8b6b5d18878cac0aeabc687d241111; 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 67d58ab4f2ccf7145f3da07e025735a09c79de1b; 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 180ff4c81faf01ec4e06082c9daa7c40518ead89; 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 804b681002ead233abf49a3efd681f5468a835f9; 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < af421e9aed3920c7ac88c24daa48606c7112feca; 4.17 · Fixed: < 4.17; 6.6.151 ≤ 6.6.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2-rc6 ≤ *
    After
    49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 4b9601595e8b6b5d18878cac0aeabc687d241111; 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 67d58ab4f2ccf7145f3da07e025735a09c79de1b; 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 180ff4c81faf01ec4e06082c9daa7c40518ead89; 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < 804b681002ead233abf49a3efd681f5468a835f9; 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb < af421e9aed3920c7ac88c24daa48606c7112feca; 4.17 · Fixed: < 4.17; 6.6.151 ≤ 6.6.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  4. SeveritySeverity changed from Unknown to Critical.
    Before
    Unknown
    After
    Critical
    CNA ↗
  5. CVSS scoreCVSS score changed from not recorded to 9.8 (CVSS 3.1 · CNA · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
    Before
    not recorded
    After
    9.8 (CVSS 3.1 · CNA · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
    CNA ↗
  6. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-59671↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-74478 · cve.blacktree.nl