BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-46306High confidence

flow_dissector: do not dissect PPPoE PFC frames

Linux · Linux

7.5HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

20 package states
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.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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.

2 current
CVE-2026-46306 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: flow_dissector: do not dissect PPPoE PFC frames
170 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
A flaw was found in the Linux kernel's flow dissector. This vulnerability allows a remote attacker to cause a Denial of Service (DoS) by sending a specially crafted Point-to-Point Protocol over Ethernet (PPPoE) Protocol Field Compression (PFC) frame to an affected system. The incorrect processing of these compressed frames leads to a memory misalignment, which can result in a kernel crash on certain architectures.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: flow_dissector: do not dissect PPPoE PFC frames RFC 2516 Section 7 states that Protocol Field Compression (PFC) is NOT RECOMMENDED for PPPoE. In practice, pppd does not support negotiating PFC for PPPoE sessions, and the flow dissector driver has assumed an uncompressed frame until the blamed commit. During the review process of that commit [1], support for PFC is suggested. However, having a compressed (1-byte) protocol field means the subsequent PPP payload is shifted by one byte, causing 4-byte misalignment for the network header and an unaligned access exception on some architectures. The exception can be reproduced by sending a PPPoE PFC frame to an ethernet interface of a MIPS board, with RPS enabled, even if no PPPoE session is active on that interface: $ 0 : 00000000 80c40000 00000000 85144817 $ 4 : 00000008 00000100 80a75758 81dc9bb8 $ 8 : 00000010 8087ae2c 0000003d 00000000 $12 : 000000e0 00000039 00000000 00000000 $16 : 85043240 80a75758 81dc9bb8 00006488 $20 : 0000002f 00000007 85144810 80a70000 $24 : 81d1bda0 00000000 $28 : 81dc8000 81dc9aa8 00000000 805ead08 Hi : 00009d51 Lo : 2163358a epc : 805e91f0 __skb_flow_dissect+0x1b0/0x1b50 ra : 805ead08 __skb_get_hash_net+0x74/0x12c Status: 11000403 KERNEL EXL IE Cause : 40800010 (ExcCode 04) BadVA : 85144817 PrId : 0001992f (MIPS 1004Kc) Call Trace: [ ] __skb_flow_dissect+0x1b0/0x1b50 [ ] __skb_get_hash_net+0x74/0x12c [ ] get_rps_cpu+0x1b8/0x3fc [ ] netif_receive_skb_list_internal+0x324/0x364 [ ] napi_complete_done+0x68/0x2a4 [ ] mtk_napi_rx+0x228/0xfec [ ] __napi_poll+0x3c/0x1c4 [ ] napi_threaded_poll_loop+0x234/0x29c [ ] napi_threaded_poll+0x8c/0xb0 [ ] kthread+0x104/0x12c [ ] ret_from_kernel_thread+0x14/0x1c Code: 02d51821 1060045b 00000000 3084000f 2c820005 144001a2 00042080 8e220000 To reduce the attack surface and maintain performance, do not process PPPoE PFC frames. [1] https://lore.kernel.org/r/20220630231016.GA392@debian.home
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
Optional official sources

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

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

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-35171

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: flow_dissector: do not dissect PPPoE PFC frames RFC 2516 Section 7 states that Protocol Field Compression (PFC) is NOT RECOMMENDED for PPPoE. In practice, pppd does not support negotiating PFC for PPPoE sessions, and the flow dissector driver has assumed an uncompressed frame until the blamed commit. During the review process of that commit [1], support for PFC is suggested. However, having a compressed (1-byte) protocol field means the subsequent PPP payload is shifted by one byte, causing 4-byte misalignment for the network header and an unaligned access exception on some architectures. The exception can be reproduced by sending a PPPoE PFC frame to an ethernet interface of a MIPS board, with RPS enabled, even if no PPPoE session is active on that interface: $ 0 : 00000000 80c40000 00000000 85144817 $ 4 : 00000008 00000100 80a75758 81dc9bb8 $ 8 : 00000010 8087ae2c 0000003d 00000000 $12 : 000000e0 00000039 00000000 00000000 $16 : 85043240 80a75758 81dc9bb8 00006488 $20 : 0000002f 00000007 85144810 80a70000 $24 : 81d1bda0 00000000 $28 : 81dc8000 81dc9aa8 00000000 805ead08 Hi : 00009d51 Lo : 2163358a epc : 805e91f0 __skb_flow_dissect+0x1b0/0x1b50 ra : 805ead08 __skb_get_hash_net+0x74/0x12c Status: 11000403 KERNEL EXL IE Cause : 40800010 (ExcCode 04) BadVA : 85144817 PrId : 0001992f (MIPS 1004Kc) Call Trace: [<805e91f0>] __skb_flow_dissect+0x1b0/0x1b50 [<805ead08>] __skb_get_hash_net+0x74/0x12c [<805ef330>] get_rps_cpu+0x1b8/0x3fc [<805fca70>] netif_receive_skb_list_internal+0x324/0x364 [<805fd120>] napi_complete_done+0x68/0x2a4 [<8058de5c>] mtk_napi_rx+0x228/0xfec [<805fd398>] __napi_poll+0x3c/0x1c4 [<805fd754>] napi_threaded_poll_loop+0x234/0x29c [<805fd848>] napi_threaded_poll+0x8c/0xb0 [<80053544>] kthread+0x104/0x12c [<80002bd8>] ret_from_kernel_thread+0x14/0x1c Code: 02d51821 1060045b 00000000 <8c640000> 3084000f 2c820005 144001a2 00042080 8e220000 To reduce the attack surface and maintain performance, do not process PPPoE PFC frames. [1] https://lore.kernel.org/r/20220630231016.GA392@debian.home

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
7.5 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: flow_dissector: do not dissect PPPoE PFC frames RFC 2516 Section 7 states that Protocol Field Compression (PFC) is NOT RECOMMENDED for PPPoE. In practice, pppd does not support negotiating PFC for PPPoE sessions, and the flow dissector driver has assumed an uncompressed frame until the blamed commit. During the review process of that commit [1], support for PFC is suggested. However, having a compressed (1-byte) protocol field means the subsequent PPP payload is shifted by one byte, causing 4-byte misalignment for the network header and an unaligned access exception on some architectures. The exception can be reproduced by sending a PPPoE PFC frame to an ethernet interface of a MIPS board, with RPS enabled, even if no PPPoE session is active on that interface: $ 0 : 00000000 80c40000 00000000 85144817 $ 4 : 00000008 00000100 80a75758 81dc9bb8 $ 8 : 00000010 8087ae2c 0000003d 00000000 $12 : 000000e0 00000039 00000000 00000000 $16 : 85043240 80a75758 81dc9bb8 00006488 $20 : 0000002f 00000007 85144810 80a70000 $24 : 81d1bda0 00000000 $28 : 81dc8000 81dc9aa8 00000000 805ead08 Hi : 00009d51 Lo : 2163358a epc : 805e91f0 __skb_flow_dissect+0x1b0/0x1b50 ra : 805ead08 __skb_get_hash_net+0x74/0x12c Status: 11000403 KERNEL EXL IE Cause : 40800010 (ExcCode 04) BadVA : 85144817 PrId : 0001992f (MIPS 1004Kc) Call Trace: [<805e91f0>] __skb_flow_dissect+0x1b0/0x1b50 [<805ead08>] __skb_get_hash_net+0x74/0x12c [<805ef330>] get_rps_cpu+0x1b8/0x3fc [<805fca70>] netif_receive_skb_list_internal+0x324/0x364 [<805fd120>] napi_complete_done+0x68/0x2a4 [<8058de5c>] mtk_napi_rx+0x228/0xfec [<805fd398>] __napi_poll+0x3c/0x1c4 [<805fd754>] napi_threaded_poll_loop+0x234/0x29c [<805fd848>] napi_threaded_poll+0x8c/0xb0 [<80053544>] kthread+0x104/0x12c [<80002bd8>] ret_from_kernel_thread+0x14/0x1c Code: 02d51821 1060045b 00000000 <8c640000> 3084000f 2c820005 144001a2 00042080 8e220000 To reduce the attack surface and maintain performance, do not process PPPoE PFC frames. [1] https://lore.kernel.org/r/20220630231016.GA392@debian.home

What

In the Linux kernel, the following vulnerability has been resolved: flow_dissector: do not dissect PPPoE PFC frames RFC 2516 Section 7 states that Protocol Field Compression (PFC) is NOT RECOMMENDED for PPPoE. In practice, pppd does not support negotiating PFC for PPPoE sessions, and the flow dissector driver has assumed an uncompressed frame until the blamed commit. During the review process of that commit [1], support for PFC is suggested. However, having a compressed (1-byte) protocol field means the subsequent PPP payload is shifted by one byte, causing 4-byte misalignment for the network header and an unaligned access exception on some architectures. The exception can be reproduced by sending a PPPoE PFC frame to an ethernet interface of a MIPS board, with RPS enabled, even if no PPPoE session is active on that interface: $ 0 : 00000000 80c40000 00000000 85144817 $ 4 : 00000008 00000100 80a75758 81dc9bb8 $ 8 : 00000010 8087ae2c 0000003d 00000000 $12 : 000000e0 00000039 00000000 00000000 $16 : 85043240 80a75758 81dc9bb8 00006488 $20 : 0000002f 00000007 85144810 80a70000 $24 : 81d1bda0 00000000 $28 : 81dc8000 81dc9aa8 00000000 805ead08 Hi : 00009d51 Lo : 2163358a epc : 805e91f0 __skb_flow_dissect+0x1b0/0x1b50 ra : 805ead08 __skb_get_hash_net+0x74/0x12c Status: 11000403 KERNEL EXL IE Cause : 40800010 (ExcCode 04) BadVA : 85144817 PrId : 0001992f (MIPS 1004Kc) Call Trace: [<805e91f0>] __skb_flow_dissect+0x1b0/0x1b50 [<805ead08>] __skb_get_hash_net+0x74/0x12c [<805ef330>] get_rps_cpu+0x1b8/0x3fc [<805fca70>] netif_receive_skb_list_internal+0x324/0x364 [<805fd120>] napi_complete_done+0x68/0x2a4 [<8058de5c>] mtk_napi_rx+0x228/0xfec [<805fd398>] __napi_poll+0x3c/0x1c4 [<805fd754>] napi_threaded_poll_loop+0x234/0x29c [<805fd848>] napi_threaded_poll+0x8c/0xb0 [<80053544>] kthread+0x104/0x12c [<80002bd8>] ret_from_kernel_thread+0x14/0x1c Code: 02d51821 1060045b 00000000 <8c640000> 3084000f 2c820005 144001a2 00042080 8e220000 To reduce the attack surface and maintain performance, do not process PPPoE PFC frames. [1] https://lore.kernel.org/r/20220630231016.GA392@debian.home

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: flow_dissector: do not dissect PPPoE PFC frames RFC 2516 Section 7 states that Protocol Field Compression (PFC) is NOT RECOMMENDED for PPPoE. In practice, pppd does not support negotiating PFC for PPPoE sessions, and the flow dissector driver has assumed an uncompressed frame until the blamed commit. During the review process of that commit [1], support for PFC is suggested. However, having a compressed (1-byte) protocol field means the subsequent PPP payload is shifted by one byte, causing 4-byte misalignment for the network header and an unaligned access exception on some architectures. The exception can be reproduced by sending a PPPoE PFC frame to an ethernet interface of a MIPS board, with RPS enabled, even if no PPPoE session is active on that interface: $ 0 : 00000000 80c40000 00000000 85144817 $ 4 : 00000008 00000100 80a75758 81dc9bb8 $ 8 : 00000010 8087ae2c 0000003d 00000000 $12 : 000000e0 00000039 00000000 00000000 $16 : 85043240 80a75758 81dc9bb8 00006488 $20 : 0000002f 00000007 85144810 80a70000 $24 : 81d1bda0 00000000 $28 : 81dc8000 81dc9aa8 00000000 805ead08 Hi : 00009d51 Lo : 2163358a epc : 805e91f0 __skb_flow_dissect+0x1b0/0x1b50 ra : 805ead08 __skb_get_hash_net+0x74/0x12c Status: 11000403 KERNEL EXL IE Cause : 40800010 (ExcCode 04) BadVA : 85144817 PrId : 0001992f (MIPS 1004Kc) Call Trace: [<805e91f0>] __skb_flow_dissect+0x1b0/0x1b50 [<805ead08>] __skb_get_hash_net+0x74/0x12c [<805ef330>] get_rps_cpu+0x1b8/0x3fc [<805fca70>] netif_receive_skb_list_internal+0x324/0x364 [<805fd120>] napi_complete_done+0x68/0x2a4 [<8058de5c>] mtk_napi_rx+0x228/0xfec [<805fd398>] __napi_poll+0x3c/0x1c4 [<805fd754>] napi_threaded_poll_loop+0x234/0x29c [<805fd848>] napi_threaded_poll+0x8c/0xb0 [<80053544>] kthread+0x104/0x12c [<80002bd8>] ret_from_kernel_thread+0x14/0x1c Code: 02d51821 1060045b 00000000 <8c640000> 3084000f 2c820005 144001a2 00042080 8e220000 To reduce the attack surface and maintain performance, do not process PPPoE PFC frames. [1] https://lore.kernel.org/r/20220630231016.GA392@debian.home

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:N/I:N/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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.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-35171Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: flow_dissector: do not dissect PPPoE PFC frames RFC 2516 Section 7 states that Protocol Field Compression (PFC) is NOT RECOMMENDED for PPPoE. In practice, pppd does not support negotiating PFC for PPPoE sessions, and the flow dissector driver has assumed an uncompressed frame until the blamed commit. During the review process of that commit [1], support for PFC is suggested. However, having a compressed (1-byte) protocol field means the subsequent PPP payload is shifted by one byte, causing 4-byte misalignment for the network header and an unaligned access exception on some architectures. The exception can be reproduced by sending a PPPoE PFC frame to an ethernet interface of a MIPS board, with RPS enabled, even if no PPPoE session is active on that interface: $ 0 : 00000000 80c40000 00000000 85144817 $ 4 : 00000008 00000100 80a75758 81dc9bb8 $ 8 : 00000010 8087ae2c 0000003d 00000000 $12 : 000000e0 00000039 00000000 00000000 $16 : 85043240 80a75758 81dc9bb8 00006488 $20 : 0000002f 00000007 85144810 80a70000 $24 : 81d1bda0 00000000 $28 : 81dc8000 81dc9aa8 00000000 805ead08 Hi : 00009d51 Lo : 2163358a epc : 805e91f0 __skb_flow_dissect+0x1b0/0x1b50 ra : 805ead08 __skb_get_hash_net+0x74/0x12c Status: 11000403 KERNEL EXL IE Cause : 40800010 (ExcCode 04) BadVA : 85144817 PrId : 0001992f (MIPS 1004Kc) Call Trace: [<805e91f0>] __skb_flow_dissect+0x1b0/0x1b50 [<805ead08>] __skb_get_hash_net+0x74/0x12c [<805ef330>] get_rps_cpu+0x1b8/0x3fc [<805fca70>] netif_receive_skb_list_internal+0x324/0x364 [<805fd120>] napi_complete_done+0x68/0x2a4 [<8058de5c>] mtk_napi_rx+0x228/0xfec [<805fd398>] __napi_poll+0x3c/0x1c4 [<805fd754>] napi_threaded_poll_loop+0x234/0x29c [<805fd848>] napi_threaded_poll+0x8c/0xb0 [<80053544>] kthread+0x104/0x12c [<80002bd8>] ret_from_kernel_thread+0x14/0x1c Code: 02d51821 1060045b 00000000 <8c640000> 3084000f 2c820005 144001a2 00042080 8e220000 To reduce the attack surface and maintain performance, do not process PPPoE PFC frames. [1] https://lore.kernel.org/r/20220630231016.GA392@debian.home

Official EUVD record
BSI · German · WID-SEC-W-2026-1827Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht bekannte Auswirkungen zu erzielen.

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

d?id=CVE-2026-46189 Référence CVE CVE-2026-46193 https://www.cve.org/CVERecord?id=CVE-2026-46193 Référence CVE CVE-2026-46234 https://www.cve.org/CVERecord?id=CVE-2026-46234 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46243 https://www.cve.org/CVERecord?id=CVE-2026-46243 Référence CVE CVE-2026-46245 https://www.cve.org/CVERecord?id=CVE-2026-46245 Référence CVE CVE-2026-46265 https://www.cve.org/CVERecord?id=CVE-2026-46265 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46292 https://www.cve.org/CVERecord?id=CVE-2026-46292 Référence CVE CVE-2026-46306 https://www.cve.org/CVERecord?id=CVE-2026-46306 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-46323 https://www.cve.org/CVERecord?id=CVE-2026-46323 Référence CVE CVE-2026-46324 https://www.cve.org/CVERecord?id=CVE-2026-46324 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=CVE-2026-46331 Référence CVE CVE-2026-46333 https://www.cve.org/CVERecord?id=CVE-2026-46333 Référence CVE CVE-2026-52910 https://www.cve.org/CVERecord?id=CVE-2026-52910 Référence CVE CVE-2026-52921 https://www.cve.org/CVERecord?id=CVE-2026-52921 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46282 Référence CVE CVE-2026-46283 https://www.cve.org/CVERecord?id=CVE-2026-46283 Référence CVE CVE-2026-46285 https://www.cve.org/CVERecord?id=CVE-2026-46285 Référence CVE CVE-2026-46286 https://www.cve.org/CVERecord?id=CVE-2026-46286 Référence CVE CVE-2026-46287 https://www.cve.org/CVERecord?id=CVE-2026-46287 Référence CVE CVE-2026-46292 https://www.cve.org/CVERecord?id=CVE-2026-46292 Référence CVE CVE-2026-46294 https://www.cve.org/CVERecord?id=CVE-2026-46294 Référence CVE CVE-2026-46296 https://www.cve.org/CVERecord?id=CVE-2026-46296 Référence CVE CVE-2026-46301 https://www.cve.org/CVERecord?id=CVE-2026-46301 Référence CVE CVE-2026-46306 https://www.cve.org/CVERecord?id=CVE-2026-46306 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=CVE-2026-46307 Référence CVE CVE-2026-46312 https://www.cve.org/CVERecord?id=CVE-2026-46312 Référence CVE CVE-2026-46313 https://www.cve.org/CVERecord?id=CVE-2026-46313 Référence CVE CVE-2026-46315 https://www.cve.org/CVERecord?id=CVE-2026-46315 Référence CVE CVE-2026-46321 https://www.cve.org/CVERecord?id=CVE-2026-46321 Référence CVE CVE-2026-46323 https://www.cve.org/CVERecord?id=CVE-2026-46323 Référence CVE CVE-2026-46324 https://www.cve.org/CVERecord?id=CVE-2026-46324 Référence CVE CVE-2026-46326 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46296 Référence CVE CVE-2026-46297 https://www.cve.org/CVERecord?id=CVE-2026-46297 Référence CVE CVE-2026-46298 https://www.cve.org/CVERecord?id=CVE-2026-46298 Référence CVE CVE-2026-46299 https://www.cve.org/CVERecord?id=CVE-2026-46299 Référence CVE CVE-2026-46301 https://www.cve.org/CVERecord?id=CVE-2026-46301 Référence CVE CVE-2026-46302 https://www.cve.org/CVERecord?id=CVE-2026-46302 Référence CVE CVE-2026-46303 https://www.cve.org/CVERecord?id=CVE-2026-46303 Référence CVE CVE-2026-46304 https://www.cve.org/CVERecord?id=CVE-2026-46304 Référence CVE CVE-2026-46305 https://www.cve.org/CVERecord?id=CVE-2026-46305 Référence CVE CVE-2026-46306 https://www.cve.org/CVERecord?id=CVE-2026-46306 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=CVE-2026-46307 Référence CVE CVE-2026-46308 https://www.cve.org/CVERecord?id=CVE-2026-46308 Référence CVE CVE-2026-46309 https://www.cve.org/CVERecord?id=CVE-2026-46309 Référence CVE CVE-2026-46310 https://www.cve.org/CVERecord?id=CVE-2026-46310 Référence CVE CVE-2026-46311 https://www.cve.org/CVERecord?id=CVE-2026-46311 Référence CVE CVE-2026-46312 https://www.cve.org/CVERecord?id=CVE-2026-46312 Référence CVE CVE-2026-46313 https://www.cve.org/CVERecord?id=CVE-2026-46313 Référence CVE CVE-2026-46314 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46296 Référence CVE CVE-2026-46297 https://www.cve.org/CVERecord?id=CVE-2026-46297 Référence CVE CVE-2026-46298 https://www.cve.org/CVERecord?id=CVE-2026-46298 Référence CVE CVE-2026-46299 https://www.cve.org/CVERecord?id=CVE-2026-46299 Référence CVE CVE-2026-46301 https://www.cve.org/CVERecord?id=CVE-2026-46301 Référence CVE CVE-2026-46302 https://www.cve.org/CVERecord?id=CVE-2026-46302 Référence CVE CVE-2026-46303 https://www.cve.org/CVERecord?id=CVE-2026-46303 Référence CVE CVE-2026-46304 https://www.cve.org/CVERecord?id=CVE-2026-46304 Référence CVE CVE-2026-46305 https://www.cve.org/CVERecord?id=CVE-2026-46305 Référence CVE CVE-2026-46306 https://www.cve.org/CVERecord?id=CVE-2026-46306 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=CVE-2026-46307 Référence CVE CVE-2026-46308 https://www.cve.org/CVERecord?id=CVE-2026-46308 Référence CVE CVE-2026-46309 https://www.cve.org/CVERecord?id=CVE-2026-46309 Référence CVE CVE-2026-46310 https://www.cve.org/CVERecord?id=CVE-2026-46310 Référence CVE CVE-2026-46311 https://www.cve.org/CVERecord?id=CVE-2026-46311 Référence CVE CVE-2026-46312 https://www.cve.org/CVERecord?id=CVE-2026-46312 Référence CVE CVE-2026-46313 https://www.cve.org/CVERecord?id=CVE-2026-46313 Référence CVE CVE-2026-46314 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46297 Référence CVE CVE-2026-46298 https://www.cve.org/CVERecord?id=CVE-2026-46298 Référence CVE CVE-2026-46299 https://www.cve.org/CVERecord?id=CVE-2026-46299 Référence CVE CVE-2026-46300 https://www.cve.org/CVERecord?id=CVE-2026-46300 Référence CVE CVE-2026-46301 https://www.cve.org/CVERecord?id=CVE-2026-46301 Référence CVE CVE-2026-46302 https://www.cve.org/CVERecord?id=CVE-2026-46302 Référence CVE CVE-2026-46303 https://www.cve.org/CVERecord?id=CVE-2026-46303 Référence CVE CVE-2026-46304 https://www.cve.org/CVERecord?id=CVE-2026-46304 Référence CVE CVE-2026-46305 https://www.cve.org/CVERecord?id=CVE-2026-46305 Référence CVE CVE-2026-46306 https://www.cve.org/CVERecord?id=CVE-2026-46306 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=CVE-2026-46307 Référence CVE CVE-2026-46308 https://www.cve.org/CVERecord?id=CVE-2026-46308 Référence CVE CVE-2026-46309 https://www.cve.org/CVERecord?id=CVE-2026-46309 Référence CVE CVE-2026-46310 https://www.cve.org/CVERecord?id=CVE-2026-46310 Référence CVE CVE-2026-46311 https://www.cve.org/CVERecord?id=CVE-2026-46311 Référence CVE CVE-2026-46312 https://www.cve.org/CVERecord?id=CVE-2026-46312 Référence CVE CVE-2026-46313 https://www.cve.org/CVERecord?id=CVE-2026-46313 Référence CVE CVE-2026-46314 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46285 Référence CVE CVE-2026-46291 https://www.cve.org/CVERecord?id=CVE-2026-46291 Référence CVE CVE-2026-46292 https://www.cve.org/CVERecord?id=CVE-2026-46292 Référence CVE CVE-2026-46294 https://www.cve.org/CVERecord?id=CVE-2026-46294 Référence CVE CVE-2026-46296 https://www.cve.org/CVERecord?id=CVE-2026-46296 Référence CVE CVE-2026-46299 https://www.cve.org/CVERecord?id=CVE-2026-46299 Référence CVE CVE-2026-46301 https://www.cve.org/CVERecord?id=CVE-2026-46301 Référence CVE CVE-2026-46303 https://www.cve.org/CVERecord?id=CVE-2026-46303 Référence CVE CVE-2026-46304 https://www.cve.org/CVERecord?id=CVE-2026-46304 Référence CVE CVE-2026-46306 https://www.cve.org/CVERecord?id=CVE-2026-46306 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=CVE-2026-46307 Référence CVE CVE-2026-46314 https://www.cve.org/CVERecord?id=CVE-2026-46314 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-46320 https://www.cve.org/CVERecord?id=CVE-2026-46320 Référence CVE CVE-2026-46321 https://www.cve.org/CVERecord?id=CVE-2026-46321 Référence CVE CVE-2026-46322 https://www.cve.org/CVERecord?id=CVE-2026-46322 Référence CVE CVE-2026-46323 https://www.cve.org/CVERecord?id=CVE-2026-46323 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0783Multiples vulnérabilités dans Microsoft Azure

ulletin de sécurité Microsoft CVE-2026-46287 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46289 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46291 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46292 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46293 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46296 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46299 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46301 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46303 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46304 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46306 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46307 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46312 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-46319 du 10 juin 2026 Bulletin de sécurité Microsoft CVE-2026-34180 du 13 juin 2026 Bulletin de sécurité Microsoft CVE-2026-42766 du 13 juin 2026 Bulletin de sécurité Microsoft CVE-2026-42767 du 13 juin 2026 Bulletin de sécurité Microsoft CVE-2026-45445 du 13 juin 2026 Bulletin de sécurité Microsoft CVE-2026-45447 du 13 juin 2026 Bulletin de sécurité Microsoft CVE-2026-7383 du 13 juin 2026 Bulletin de sécurité Microsoft CVE-2026-9076 du 13 juin 2026 Bulletin de séc

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.
Patch available
Affected
kernel as a component of Red Hat Enterprise Linux 6; kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6; kernel-bootwrapper as a component of Red Hat Enterprise Linux 6; kernel-debug as a component of Red Hat Enterprise Linux 6; kernel-debug-devel as a component of Red Hat Enterprise Linux 6; kernel-devel as a component of Red Hat Enterprise Linux 6; kernel-doc as a component of Red Hat Enterprise Linux 6; kernel-firmware as a component of Red Hat Enterprise Linux 6; kernel-headers as a component of Red Hat Enterprise Linux 6; kernel-kdump as a component of Red Hat Enterprise Linux 6; kernel-kdump-devel as a component of Red Hat Enterprise Linux 6; kernel.src as a component of Red Hat Enterprise Linux 6; perf as a component of Red Hat Enterprise Linux 6; python-perf as a component of Red Hat Enterprise Linux 6; bpftool as a component of Red Hat Enterprise Linux 8; kernel as a component of Red Hat Enterprise Linux 8; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 8; kernel-abi-whitelists as a component of Red Hat Enterprise Linux 8; kernel-core as a component of Red Hat Enterprise Linux 8; kernel-cross-headers as a component of Red Hat Enterprise Linux 8; kernel-debug as a component of Red Hat Enterprise Linux 8; kernel-debug-core as a component of Red Hat Enterprise Linux 8; kernel-debug-devel as a component of Red Hat Enterprise Linux 8; kernel-debug-modules as a component of Red Hat Enterprise Linux 8; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 8; kernel-debug-modules-internal as a component of Red Hat Enterprise Linux 8; kernel-devel as a component of Red Hat Enterprise Linux 8; kernel-doc as a component of Red Hat Enterprise Linux 8; kernel-headers as a component of Red Hat Enterprise Linux 8; kernel-ipaclones-internal as a component of Red Hat Enterprise Linux 8; and 140 more
Fixed
kernel-64k-debug-debuginfo-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-matched-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debuginfo-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-matched-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-aarch64-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-ppc64le-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-s390x-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-x86_64-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); and 279 more
Action
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
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 8 Jun 2026 · Last source change 8 Sept 2026, 08:49 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-14
European sourceENISA EUVD · EUVD-2026-35171
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceUnavailable
NVD statusNVD modified after enrichment

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 →

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

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-35171↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update 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-46306 · cve.blacktree.nl