BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2021-46955High confidence

openvswitch: fix stack OOB read while fragmenting IPv4 packets

Linux · Linux

8.2HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state 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 severityHighOperational priority:High, 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.75% 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 30 daysRemediation target: Within 180 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 1 structured product or package state 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.

5 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 1 affected package state 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.5.10.38-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.10.38-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.10.38-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.10.38-1Debian Security Tracker ↗Source updated 6 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
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-2021-46955 · CSAF 2.0 · revision 77 · interimSUSE Product Security TeamCVE-2021-46955
15 known affected

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

  • SLES 15 SP1 CHOST Images for Amazon EC2
  • SLES 15 SP2 CHOST Images for Amazon EC2
  • SLES 15 SP3 CHOST Images for Amazon EC2
  • SLES 15 SP4 CHOST Images for Amazon EC2
  • SLES 15 SP5 CHOST Images for Amazon EC2
  • SLES 15 SP1 CHOST Images for Google
  • SLES 15 SP2 CHOST Images for Google
  • SLES 15 SP3 CHOST Images for Google
  • SLES 15 SP4 CHOST Images for Google
  • SLES 15 SP5 CHOST Images for Google
  • SLES 15 SP1 CHOST Images for Microsoft Azure
  • SLES 15 SP2 CHOST Images for Microsoft Azure
Summary
In the Linux kernel, the following vulnerability has been resolved: openvswitch: fix stack OOB read while fragmenting IPv4 packets running openvswitch on kernels built with KASAN, it's possible to see the following splat while testing fragmentation of IPv4 packets: BUG: KASAN: stack-out-of-bounds in ip_do_fragment+0x1b03/0x1f60 Read of size 1 at addr ffff888112fc713c by task handler2/1367 CPU: 0 PID: 1367 Comm: handler2 Not tainted 5.12.0-rc6+ #418 Hardware name: Red Hat KVM, BIOS 1.11.1-4.module+el8.1.0+4066+0f1aadab 04/01/2014 Call Trace: dump_stack+0x92/0xc1 print_address_description.constprop.7+0x1a/0x150 kasan_report.cold.13+0x7f/0x111 ip_do_fragment+0x1b03/0x1f60 ovs_fragment+0x5bf/0x840 [openvswitch] do_execute_actions+0x1bd5/0x2400 [openvswitch] ovs_execute_actions+0xc8/0x3d0 [openvswitch] ovs_packet_cmd_execute+0xa39/0x1150 [openvswitch] genl_family_rcv_msg_doit.isra.15+0x227/0x2d0 genl_rcv_msg+0x287/0x490 netlink_rcv_skb+0x120/0x380 genl_rcv+0x24/0x40 netlink_unicast+0x439/0x630 netlink_sendmsg+0x719/0xbf0 sock_sendmsg+0xe2/0x110 ____sys_sendmsg+0x5ba/0x890 ___sys_sendmsg+0xe9/0x160 __sys_sendmsg+0xd3/0x170 do_syscall_64+0x33/0x40 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f957079db07 Code: c3 66 90 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 eb ec ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 24 ed ff ff 48 RSP: 002b:00007f956ce35a50 EFLAGS: 00000293 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 0000000000000019 RCX: 00007f957079db07 RDX: 0000000000000000 RSI: 00007f956ce35ae0 RDI: 0000000000000019 RBP: 00007f956ce35ae0 R08: 0000000000000000 R09: 00007f9558006730 R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000 R13: 00007f956ce37308 R14: 00007f956ce35f80 R15: 00007f956ce35ae0 The buggy address belongs to the page: page:00000000af2a1d93 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x112fc7 flags: 0x17ffffc0000000() raw: 0017ffffc0000000 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected addr ffff888112fc713c is located in stack of task handler2/1367 at offset 180 in frame: ovs_fragment+0x0/0x840 [openvswitch] this frame has 2 objects: [32, 144) 'ovs_dst' [192, 424) 'ovs_rt' Memory state around the buggy address: ffff888112fc7000: f3 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff888112fc7080: 00 f1 f1 f1 f1 00 00 00 00 00 00 00 00 00 00 00 >ffff888112fc7100: 00 00 00 f2 f2 f2 f2 f2 f2 00 00 00 00 00 00 00 ^ ffff888112fc7180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff888112fc7200: 00 00 00 00 00 00 f2 f2 f2 00 00 00 00 00 00 00 for IPv4 packets, ovs_fragment() uses a temporary struct dst_entry. Then, in the following call graph: ip_do_fragment() ip_skb_dst_mtu() ip_dst_mtu_maybe_forward() ip_mtu_locked() the pointer to struct dst_entry is used as pointer to struct rtable: this turns the access to struct members like rt_mtu_locked into an OOB read in the stack. Fix this changing the temporary variable used for IPv4 packets in ovs_fragment(), similarly to what is done for IPv6 few lines below.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-2021-33603

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

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
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state 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: openvswitch: fix stack OOB read while fragmenting IPv4 packets running openvswitch on kernels built with KASAN, it's possible to see the following splat while testing fragmentation of IPv4 packets: BUG: KASAN: stack-out-of-bounds in ip_do_fragment+0x1b03/0x1f60 Read of size 1 at addr ffff888112fc713c by task handler2/1367 CPU: 0 PID: 1367 Comm: handler2 Not tainted 5.12.0-rc6+ #418 Hardware name: Red Hat KVM, BIOS 1.11.1-4.module+el8.1.0+4066+0f1aadab 04/01/2014 Call Trace: dump_stack+0x92/0xc1 print_address_description.constprop.7+0x1a/0x150 kasan_report.cold.13+0x7f/0x111 ip_do_fragment+0x1b03/0x1f60 ovs_fragment+0x5bf/0x840 [openvswitch] do_execute_actions+0x1bd5/0x2400 [openvswitch] ovs_execute_actions+0xc8/0x3d0 [openvswitch] ovs_packet_cmd_execute+0xa39/0x1150 [openvswitch] genl_family_rcv_msg_doit.isra.15+0x227/0x2d0 genl_rcv_msg+0x287/0x490 netlink_rcv_skb+0x120/0x380 genl_rcv+0x24/0x40 netlink_unicast+0x439/0x630 netlink_sendmsg+0x719/0xbf0 sock_sendmsg+0xe2/0x110 ____sys_sendmsg+0x5ba/0x890 ___sys_sendmsg+0xe9/0x160 __sys_sendmsg+0xd3/0x170 do_syscall_64+0x33/0x40 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f957079db07 Code: c3 66 90 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 eb ec ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 24 ed ff ff 48 RSP: 002b:00007f956ce35a50 EFLAGS: 00000293 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 0000000000000019 RCX: 00007f957079db07 RDX: 0000000000000000 RSI: 00007f956ce35ae0 RDI: 0000000000000019 RBP: 00007f956ce35ae0 R08: 0000000000000000 R09: 00007f9558006730 R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000 R13: 00007f956ce37308 R14: 00007f956ce35f80 R15: 00007f956ce35ae0 The buggy address belongs to the page: page:00000000af2a1d93 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x112fc7 flags: 0x17ffffc0000000() raw: 0017ffffc0000000 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected addr ffff888112fc713c is located in stack of task handler2/1367 at offset 180 in frame: ovs_fragment+0x0/0x840 [openvswitch] this frame has 2 objects: [32, 144) 'ovs_dst' [192, 424) 'ovs_rt' Memory state around the buggy address: ffff888112fc7000: f3 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff888112fc7080: 00 f1 f1 f1 f1 00 00 00 00 00 00 00 00 00 00 00 >ffff888112fc7100: 00 00 00 f2 f2 f2 f2 f2 f2 00 00 00 00 00 00 00 ^ ffff888112fc7180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff888112fc7200: 00 00 00 00 00 00 f2 f2 f2 00 00 00 00 00 00 00 for IPv4 packets, ovs_fragment() uses a temporary struct dst_entry. Then, in the following call graph: ip_do_fragment() ip_skb_dst_mtu() ip_dst_mtu_maybe_forward() ip_mtu_locked() the pointer to struct dst_entry is used as pointer to struct rtable: this turns the access to struct members like rt_mtu_locked into an OOB read in the stack. Fix this changing the temporary variable used for IPv4 packets in ovs_fragment(), similarly to what is done for IPv6 few lines below.

What

In the Linux kernel, the following vulnerability has been resolved: openvswitch: fix stack OOB read while fragmenting IPv4 packets running openvswitch on kernels built with KASAN, it's possible to see the following splat while testing fragmentation of IPv4 packets: BUG: KASAN: stack-out-of-bounds in ip_do_fragment+0x1b03/0x1f60 Read of size 1 at addr ffff888112fc713c by task handler2/1367 CPU: 0 PID: 1367 Comm: handler2 Not tainted 5.12.0-rc6+ #418 Hardware name: Red Hat KVM, BIOS 1.11.1-4.module+el8.1.0+4066+0f1aadab 04/01/2014 Call Trace: dump_stack+0x92/0xc1 print_address_description.constprop.7+0x1a/0x150 kasan_report.cold.13+0x7f/0x111 ip_do_fragment+0x1b03/0x1f60 ovs_fragment+0x5bf/0x840 [openvswitch] do_execute_actions+0x1bd5/0x2400 [openvswitch] ovs_execute_actions+0xc8/0x3d0 [openvswitch] ovs_packet_cmd_execute+0xa39/0x1150 [openvswitch] genl_family_rcv_msg_doit.isra.15+0x227/0x2d0 genl_rcv_msg+0x287/0x490 netlink_rcv_skb+0x120/0x380 genl_rcv+0x24/0x40 netlink_unicast+0x439/0x630 netlink_sendmsg+0x719/0xbf0 sock_sendmsg+0xe2/0x110 ____sys_sendmsg+0x5ba/0x890 ___sys_sendmsg+0xe9/0x160 __sys_sendmsg+0xd3/0x170 do_syscall_64+0x33/0x40 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f957079db07 Code: c3 66 90 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 eb ec ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 24 ed ff ff 48 RSP: 002b:00007f956ce35a50 EFLAGS: 00000293 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 0000000000000019 RCX: 00007f957079db07 RDX: 0000000000000000 RSI: 00007f956ce35ae0 RDI: 0000000000000019 RBP: 00007f956ce35ae0 R08: 0000000000000000 R09: 00007f9558006730 R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000 R13: 00007f956ce37308 R14: 00007f956ce35f80 R15: 00007f956ce35ae0 The buggy address belongs to the page: page:00000000af2a1d93 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x112fc7 flags: 0x17ffffc0000000() raw: 0017ffffc0000000 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected addr ffff888112fc713c is located in stack of task handler2/1367 at offset 180 in frame: ovs_fragment+0x0/0x840 [openvswitch] this frame has 2 objects: [32, 144) 'ovs_dst' [192, 424) 'ovs_rt' Memory state around the buggy address: ffff888112fc7000: f3 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff888112fc7080: 00 f1 f1 f1 f1 00 00 00 00 00 00 00 00 00 00 00 >ffff888112fc7100: 00 00 00 f2 f2 f2 f2 f2 f2 00 00 00 00 00 00 00 ^ ffff888112fc7180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff888112fc7200: 00 00 00 00 00 00 f2 f2 f2 00 00 00 00 00 00 00 for IPv4 packets, ovs_fragment() uses a temporary struct dst_entry. Then, in the following call graph: ip_do_fragment() ip_skb_dst_mtu() ip_dst_mtu_maybe_forward() ip_mtu_locked() the pointer to struct dst_entry is used as pointer to struct rtable: this turns the access to struct members like rt_mtu_locked into an OOB read in the stack. Fix this changing the temporary variable used for IPv4 packets in ovs_fragment(), similarly to what is done for IPv6 few lines below.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

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: openvswitch: fix stack OOB read while fragmenting IPv4 packets running openvswitch on kernels built with KASAN, it's possible to see the following splat while testing fragmentation of IPv4 packets: BUG: KASAN: stack-out-of-bounds in ip_do_fragment+0x1b03/0x1f60 Read of size 1 at addr ffff888112fc713c by task handler2/1367 CPU: 0 PID: 1367 Comm: handler2 Not tainted 5.12.0-rc6+ #418 Hardware name: Red Hat KVM, BIOS 1.11.1-4.module+el8.1.0+4066+0f1aadab 04/01/2014 Call Trace: dump_stack+0x92/0xc1 print_address_description.constprop.7+0x1a/0x150 kasan_report.cold.13+0x7f/0x111 ip_do_fragment+0x1b03/0x1f60 ovs_fragment+0x5bf/0x840 [openvswitch] do_execute_actions+0x1bd5/0x2400 [openvswitch] ovs_execute_actions+0xc8/0x3d0 [openvswitch] ovs_packet_cmd_execute+0xa39/0x1150 [openvswitch] genl_family_rcv_msg_doit.isra.15+0x227/0x2d0 genl_rcv_msg+0x287/0x490 netlink_rcv_skb+0x120/0x380 genl_rcv+0x24/0x40 netlink_unicast+0x439/0x630 netlink_sendmsg+0x719/0xbf0 sock_sendmsg+0xe2/0x110 ____sys_sendmsg+0x5ba/0x890 ___sys_sendmsg+0xe9/0x160 __sys_sendmsg+0xd3/0x170 do_syscall_64+0x33/0x40 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f957079db07 Code: c3 66 90 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 eb ec ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 24 ed ff ff 48 RSP: 002b:00007f956ce35a50 EFLAGS: 00000293 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 0000000000000019 RCX: 00007f957079db07 RDX: 0000000000000000 RSI: 00007f956ce35ae0 RDI: 0000000000000019 RBP: 00007f956ce35ae0 R08: 0000000000000000 R09: 00007f9558006730 R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000 R13: 00007f956ce37308 R14: 00007f956ce35f80 R15: 00007f956ce35ae0 The buggy address belongs to the page: page:00000000af2a1d93 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x112fc7 flags: 0x17ffffc0000000() raw: 0017ffffc0000000 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected addr ffff888112fc713c is located in stack of task handler2/1367 at offset 180 in frame: ovs_fragment+0x0/0x840 [openvswitch] this frame has 2 objects: [32, 144) 'ovs_dst' [192, 424) 'ovs_rt' Memory state around the buggy address: ffff888112fc7000: f3 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff888112fc7080: 00 f1 f1 f1 f1 00 00 00 00 00 00 00 00 00 00 00 >ffff888112fc7100: 00 00 00 f2 f2 f2 f2 f2 f2 00 00 00 00 00 00 00 ^ ffff888112fc7180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff888112fc7200: 00 00 00 00 00 00 f2 f2 f2 00 00 00 00 00 00 00 for IPv4 packets, ovs_fragment() uses a temporary struct dst_entry. Then, in the following call graph: ip_do_fragment() ip_skb_dst_mtu() ip_dst_mtu_maybe_forward() ip_mtu_locked() the pointer to struct dst_entry is used as pointer to struct rtable: this turns the access to struct members like rt_mtu_locked into an OOB read in the stack. Fix this changing the temporary variable used for IPv4 packets in ovs_fragment(), similarly to what is done for IPv6 few lines below.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

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 → Out-of-bounds Read → 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: a standard category for the underlying weakness.
CWE-125 ↗

CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.

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:L/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.CLowConfidentiality impact: A successful attack can cause a limited loss.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.
NetworkUnauthenticatedCWE-125
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-0225Dell PowerProtect Data Domain: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell PowerProtect Data Domain ausnutzen, um erhöhte Rechte zu erlangen, einen Denial-of-Service-Zustand herbeizuführen und einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-0500Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240228Security Bulletin 28 Feb 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 28 Feb 2024, published on 28 February 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

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

0289-1 du 29 janvier 2025 https://www.suse.com/support/update/announcement/2025/suse-su-20250289-1 Référence CVE CVE-2020-12770 https://www.cve.org/CVERecord?id=CVE-2020-12770 Référence CVE CVE-2020-36788 https://www.cve.org/CVERecord?id=CVE-2020-36788 Référence CVE CVE-2021-34556 https://www.cve.org/CVERecord?id=CVE-2021-34556 Référence CVE CVE-2021-35477 https://www.cve.org/CVERecord?id=CVE-2021-35477 Référence CVE CVE-2021-38160 https://www.cve.org/CVERecord?id=CVE-2021-38160 Référence CVE CVE-2021-4148 https://www.cve.org/CVERecord?id=CVE-2021-4148 Référence CVE CVE-2021-42327 https://www.cve.org/CVERecord?id=CVE-2021-42327 Référence CVE CVE-2021-46955 https://www.cve.org/CVERecord?id=CVE-2021-46955 Référence CVE CVE-2021-47202 https://www.cve.org/CVERecord?id=CVE-2021-47202 Référence CVE CVE-2021-47291 https://www.cve.org/CVERecord?id=CVE-2021-47291 Référence CVE CVE-2021-47365 https://www.cve.org/CVERecord?id=CVE-2021-47365 Référence CVE CVE-2021-47378 https://www.cve.org/CVERecord?id=CVE-2021-47378 Référence CVE CVE-2021-47383 https://www.cve.org/CVERecord?id=CVE-2021-47383 Référence CVE CVE-2021-47402 https://www.cve.org/CVERecord?id=CVE-2021-47402 Référence CVE CVE-2021-47489 https://www.cve.org/CVERecord?id=CVE-2021-47489 Référence CVE CVE-2021-47491 https://www.cve.org/CVERecord?id=

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

nvier 2025 https://www.suse.com/support/update/announcement/2025/suse-su-20250136-1 Bulletin de sécurité SUSE SUSE-SU-2025:0137-1 du 16 janvier 2025 https://www.suse.com/support/update/announcement/2025/suse-su-20250137-1 Bulletin de sécurité SUSE SUSE-SU-2025:0138-1 du 16 janvier 2025 https://www.suse.com/support/update/announcement/2025/suse-su-20250138-1 Bulletin de sécurité SUSE SUSE-SU-2025:0146-1 du 16 janvier 2025 https://www.suse.com/support/update/announcement/2025/suse-su-20250146-1 Bulletin de sécurité SUSE SUSE-SU-2025:0150-1 du 16 janvier 2025 https://www.suse.com/support/update/announcement/2025/suse-su-20250150-1 Référence CVE CVE-2021-46955 https://www.cve.org/CVERecord?id=CVE-2021-46955 Référence CVE CVE-2021-47291 https://www.cve.org/CVERecord?id=CVE-2021-47291 Référence CVE CVE-2021-47378 https://www.cve.org/CVERecord?id=CVE-2021-47378 Référence CVE CVE-2021-47383 https://www.cve.org/CVERecord?id=CVE-2021-47383 Référence CVE CVE-2021-47402 https://www.cve.org/CVERecord?id=CVE-2021-47402 Référence CVE CVE-2021-47517 https://www.cve.org/CVERecord?id=CVE-2021-47517 Référence CVE CVE-2021-47598 https://www.cve.org/CVERecord?id=CVE-2021-47598 Référence CVE CVE-2022-48651 https://www.cve.org/CVERecord?id=CVE-2022-48651 Référence CVE CVE-2022-48662 https://www.cve.org/CVERecord?id=

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

e 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20244265-1 Bulletin de sécurité SUSE SUSE-SU-2024:4266-1 du 09 décembre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20244266-1 Bulletin de sécurité SUSE SUSE-SU-2024:4268-1 du 09 décembre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20244268-1 Bulletin de sécurité SUSE SUSE-SU-2024:4275-1 du 10 décembre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20244275-1 Bulletin de sécurité SUSE SUSE-SU-2024:4276-1 du 10 décembre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20244276-1 Référence CVE CVE-2021-46955 https://www.cve.org/CVERecord?id=CVE-2021-46955 Référence CVE CVE-2021-47291 https://www.cve.org/CVERecord?id=CVE-2021-47291 Référence CVE CVE-2021-47378 https://www.cve.org/CVERecord?id=CVE-2021-47378 Référence CVE CVE-2021-47383 https://www.cve.org/CVERecord?id=CVE-2021-47383 Référence CVE CVE-2021-47402 https://www.cve.org/CVERecord?id=CVE-2021-47402 Référence CVE CVE-2021-47517 https://www.cve.org/CVERecord?id=CVE-2021-47517 Référence CVE CVE-2021-47598 https://www.cve.org/CVERecord?id=CVE-2021-47598 Référence CVE CVE-2021-47600 https://www.cve.org/CVERecord?id=CVE-2021-47600 Référence CVE CVE-2022-48651 https://www.cve.org/CVERecord?id=

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

tobre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20243836-1 Bulletin de sécurité SUSE SUSE-SU-2024:3837-1 du 30 octobre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20243837-1 Bulletin de sécurité SUSE SUSE-SU-2024:3840-1 du 30 octobre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20243840-1 Bulletin de sécurité SUSE SUSE-SU-2024:3838-1 du 31 octobre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20243838-1 Bulletin de sécurité SUSE SUSE-SU-2024:3842-1 du 31 octobre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20243842-1 Référence CVE CVE-2021-46955 https://www.cve.org/CVERecord?id=CVE-2021-46955 Référence CVE CVE-2021-47291 https://www.cve.org/CVERecord?id=CVE-2021-47291 Référence CVE CVE-2021-47378 https://www.cve.org/CVERecord?id=CVE-2021-47378 Référence CVE CVE-2021-47383 https://www.cve.org/CVERecord?id=CVE-2021-47383 Référence CVE CVE-2021-47402 https://www.cve.org/CVERecord?id=CVE-2021-47402 Référence CVE CVE-2021-47598 https://www.cve.org/CVERecord?id=CVE-2021-47598 Référence CVE CVE-2021-47600 https://www.cve.org/CVERecord?id=CVE-2021-47600 Référence CVE CVE-2022-48651 https://www.cve.org/CVERecord?id=CVE-2022-48651 Référence CVE CVE-2022-48662 https://www.cve.org/CVERecord?id=

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

tobre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20243639-1 Bulletin de sécurité SUSE SUSE-SU-2024:3640-1 du 15 octobre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20243640-1 Bulletin de sécurité SUSE SUSE-SU-2024:3641-1 du 15 octobre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20243641-1 Bulletin de sécurité SUSE SUSE-SU-2024:3642-1 du 15 octobre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20243642-1 Bulletin de sécurité SUSE SUSE-SU-2024:3643-1 du 16 octobre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20243643-1 Référence CVE CVE-2021-46955 https://www.cve.org/CVERecord?id=CVE-2021-46955 Référence CVE CVE-2021-47291 https://www.cve.org/CVERecord?id=CVE-2021-47291 Référence CVE CVE-2021-47378 https://www.cve.org/CVERecord?id=CVE-2021-47378 Référence CVE CVE-2021-47383 https://www.cve.org/CVERecord?id=CVE-2021-47383 Référence CVE CVE-2021-47402 https://www.cve.org/CVERecord?id=CVE-2021-47402 Référence CVE CVE-2022-48651 https://www.cve.org/CVERecord?id=CVE-2022-48651 Référence CVE CVE-2022-48662 https://www.cve.org/CVERecord?id=CVE-2022-48662 Référence CVE CVE-2023-1829 https://www.cve.org/CVERecord?id=CVE-2023-1829 Référence CVE CVE-2023-52340 https://www.cve.org/CVERecord?id=CV

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

tobre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20243704-1 Bulletin de sécurité SUSE SUSE-SU-2024:3706-1 du 16 octobre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20243706-1 Bulletin de sécurité SUSE SUSE-SU-2024:3707-1 du 16 octobre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20243707-1 Bulletin de sécurité SUSE SUSE-SU-2024:3708-1 du 16 octobre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20243708-1 Bulletin de sécurité SUSE SUSE-SU-2024:3710-1 du 16 octobre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20243710-1 Référence CVE CVE-2021-46955 https://www.cve.org/CVERecord?id=CVE-2021-46955 Référence CVE CVE-2021-47291 https://www.cve.org/CVERecord?id=CVE-2021-47291 Référence CVE CVE-2021-47378 https://www.cve.org/CVERecord?id=CVE-2021-47378 Référence CVE CVE-2021-47383 https://www.cve.org/CVERecord?id=CVE-2021-47383 Référence CVE CVE-2021-47402 https://www.cve.org/CVERecord?id=CVE-2021-47402 Référence CVE CVE-2022-48651 https://www.cve.org/CVERecord?id=CVE-2022-48651 Référence CVE CVE-2022-48662 https://www.cve.org/CVERecord?id=CVE-2022-48662 Référence CVE CVE-2023-1829 https://www.cve.org/CVERecord?id=CVE-2023-1829 Référence CVE CVE-2023-52340 https://www.cve.org/CVERecord?id=CV

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un attaquant de provoquer une élévation de privilèges, une atteinte à la confidentialité des données et un contournement de la politique de sécurité.

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

2843-1 du 08 août 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20242843-1 Bulletin de sécurité SUSE SUSE-SU-2024:2850-1 du 08 août 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20242850-1 Bulletin de sécurité SUSE SUSE-SU-2024:2851-1 du 08 août 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20242851-1 Bulletin de sécurité SUSE SUSE-SU-2024:2852-1 du 08 août 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20242852-1 Bulletin de sécurité SUSE SUSE-SU-2024:2853-1 du 08 août 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20242853-1 Référence CVE CVE-2021-46955 https://www.cve.org/CVERecord?id=CVE-2021-46955 Référence CVE CVE-2021-47383 https://www.cve.org/CVERecord?id=CVE-2021-47383 Référence CVE CVE-2022-48651 https://www.cve.org/CVERecord?id=CVE-2022-48651 Référence CVE CVE-2023-1829 https://www.cve.org/CVERecord?id=CVE-2023-1829 Référence CVE CVE-2023-38417 https://www.cve.org/CVERecord?id=CVE-2023-38417 Référence CVE CVE-2023-47210 https://www.cve.org/CVERecord?id=CVE-2023-47210 Référence CVE CVE-2023-51780 https://www.cve.org/CVERecord?id=CVE-2023-51780 Référence CVE CVE-2023-52340 https://www.cve.org/CVERecord?id=CVE-2023-52340 Référence CVE CVE-2023-52435 https://www.cve.org/CVERecord?id=CV

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

n de sécurité SUSE SUSE-SU-2024:2558-1 du 18 juillet 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20242558-1 Bulletin de sécurité SUSE SUSE-SU-2024:2559-1 du 18 juillet 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20242559-1 Bulletin de sécurité SUSE SUSE-SU-2024:2561-1 du 18 juillet 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20242561-1 Référence CVE CVE-2020-10135 https://www.cve.org/CVERecord?id=CVE-2020-10135 Référence CVE CVE-2021-43389 https://www.cve.org/CVERecord?id=CVE-2021-43389 Référence CVE CVE-2021-4439 https://www.cve.org/CVERecord?id=CVE-2021-4439 Référence CVE CVE-2021-46955 https://www.cve.org/CVERecord?id=CVE-2021-46955 Référence CVE CVE-2021-47103 https://www.cve.org/CVERecord?id=CVE-2021-47103 Référence CVE CVE-2021-47145 https://www.cve.org/CVERecord?id=CVE-2021-47145 Référence CVE CVE-2021-47191 https://www.cve.org/CVERecord?id=CVE-2021-47191 Référence CVE CVE-2021-47193 https://www.cve.org/CVERecord?id=CVE-2021-47193 Référence CVE CVE-2021-47201 https://www.cve.org/CVERecord?id=CVE-2021-47201 Référence CVE CVE-2021-47267 https://www.cve.org/CVERecord?id=CVE-2021-47267 Référence CVE CVE-2021-47270 https://www.cve.org/CVERecord?id=CVE-2021-47270 Référence CVE CVE-2021-47275 https://www.cve.org/CVERecord?id=

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

4:2411-1 du 11 juillet 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20242411-1 Référence CVE CVE-2020-10135 https://www.cve.org/CVERecord?id=CVE-2020-10135 Référence CVE CVE-2021-26345 https://www.cve.org/CVERecord?id=CVE-2021-26345 Référence CVE CVE-2021-3896 https://www.cve.org/CVERecord?id=CVE-2021-3896 Référence CVE CVE-2021-43389 https://www.cve.org/CVERecord?id=CVE-2021-43389 Référence CVE CVE-2021-4439 https://www.cve.org/CVERecord?id=CVE-2021-4439 Référence CVE CVE-2021-46766 https://www.cve.org/CVERecord?id=CVE-2021-46766 Référence CVE CVE-2021-46774 https://www.cve.org/CVERecord?id=CVE-2021-46774 Référence CVE CVE-2021-46955 https://www.cve.org/CVERecord?id=CVE-2021-46955 Référence CVE CVE-2021-47089 https://www.cve.org/CVERecord?id=CVE-2021-47089 Référence CVE CVE-2021-47103 https://www.cve.org/CVERecord?id=CVE-2021-47103 Référence CVE CVE-2021-47191 https://www.cve.org/CVERecord?id=CVE-2021-47191 Référence CVE CVE-2021-47193 https://www.cve.org/CVERecord?id=CVE-2021-47193 Référence CVE CVE-2021-47247 https://www.cve.org/CVERecord?id=CVE-2021-47247 Référence CVE CVE-2021-47267 https://www.cve.org/CVERecord?id=CVE-2021-47267 Référence CVE CVE-2021-47270 https://www.cve.org/CVERecord?id=CVE-2021-47270 Référence CVE CVE-2021-47293 https://www.cve.org/CVERecord?id=

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

pdate/announcement/2024/suse-su-20242217-1 Bulletin de sécurité SUSE SUSE-SU-2024:2221-1 du 25 juin 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20242221-1 Référence CVE CVE-2020-36788 https://www.cve.org/CVERecord?id=CVE-2020-36788 Référence CVE CVE-2021-3743 https://www.cve.org/CVERecord?id=CVE-2021-3743 Référence CVE CVE-2021-39698 https://www.cve.org/CVERecord?id=CVE-2021-39698 Référence CVE CVE-2021-4148 https://www.cve.org/CVERecord?id=CVE-2021-4148 Référence CVE CVE-2021-43056 https://www.cve.org/CVERecord?id=CVE-2021-43056 Référence CVE CVE-2021-46933 https://www.cve.org/CVERecord?id=CVE-2021-46933 Référence CVE CVE-2021-46955 https://www.cve.org/CVERecord?id=CVE-2021-46955 Référence CVE CVE-2021-47074 https://www.cve.org/CVERecord?id=CVE-2021-47074 Référence CVE CVE-2021-47104 https://www.cve.org/CVERecord?id=CVE-2021-47104 Référence CVE CVE-2021-47113 https://www.cve.org/CVERecord?id=CVE-2021-47113 Référence CVE CVE-2021-47131 https://www.cve.org/CVERecord?id=CVE-2021-47131 Référence CVE CVE-2021-47162 https://www.cve.org/CVERecord?id=CVE-2021-47162 Référence CVE CVE-2021-47171 https://www.cve.org/CVERecord?id=CVE-2021-47171 Référence CVE CVE-2021-47188 https://www.cve.org/CVERecord?id=CVE-2021-47188 Référence CVE CVE-2021-47192 https://www.cve.org/CVERecord?id=

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un attaquant de provoquer une élévation de privilèges, une atteinte à la confidentialité des données et un contournement de la politique de sécurité.

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

2024:2019-1 du 13 juin 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20242019-1 Référence CVE CVE-2020-36788 https://www.cve.org/CVERecord?id=CVE-2020-36788 Référence CVE CVE-2021-3743 https://www.cve.org/CVERecord?id=CVE-2021-3743 Référence CVE CVE-2021-39698 https://www.cve.org/CVERecord?id=CVE-2021-39698 Référence CVE CVE-2021-4148 https://www.cve.org/CVERecord?id=CVE-2021-4148 Référence CVE CVE-2021-42327 https://www.cve.org/CVERecord?id=CVE-2021-42327 Référence CVE CVE-2021-43056 https://www.cve.org/CVERecord?id=CVE-2021-43056 Référence CVE CVE-2021-46933 https://www.cve.org/CVERecord?id=CVE-2021-46933 Référence CVE CVE-2021-46955 https://www.cve.org/CVERecord?id=CVE-2021-46955 Référence CVE CVE-2021-47074 https://www.cve.org/CVERecord?id=CVE-2021-47074 Référence CVE CVE-2021-47104 https://www.cve.org/CVERecord?id=CVE-2021-47104 Référence CVE CVE-2021-47113 https://www.cve.org/CVERecord?id=CVE-2021-47113 Référence CVE CVE-2021-47131 https://www.cve.org/CVERecord?id=CVE-2021-47131 Référence CVE CVE-2021-47162 https://www.cve.org/CVERecord?id=CVE-2021-47162 Référence CVE CVE-2021-47171 https://www.cve.org/CVERecord?id=CVE-2021-47171 Référence CVE CVE-2021-47188 https://www.cve.org/CVERecord?id=CVE-2021-47188 Référence CVE CVE-2021-47192 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2021-23134 Référence CVE CVE-2021-46904 https://www.cve.org/CVERecord?id=CVE-2021-46904 Référence CVE CVE-2021-46905 https://www.cve.org/CVERecord?id=CVE-2021-46905 Référence CVE CVE-2021-46907 https://www.cve.org/CVERecord?id=CVE-2021-46907 Référence CVE CVE-2021-46909 https://www.cve.org/CVERecord?id=CVE-2021-46909 Référence CVE CVE-2021-46938 https://www.cve.org/CVERecord?id=CVE-2021-46938 Référence CVE CVE-2021-46939 https://www.cve.org/CVERecord?id=CVE-2021-46939 Référence CVE CVE-2021-46941 https://www.cve.org/CVERecord?id=CVE-2021-46941 Référence CVE CVE-2021-46950 https://www.cve.org/CVERecord?id=CVE-2021-46950 Référence CVE CVE-2021-46955 https://www.cve.org/CVERecord?id=CVE-2021-46955 Référence CVE CVE-2021-46958 https://www.cve.org/CVERecord?id=CVE-2021-46958 Référence CVE CVE-2021-46960 https://www.cve.org/CVERecord?id=CVE-2021-46960 Référence CVE CVE-2021-46963 https://www.cve.org/CVERecord?id=CVE-2021-46963 Référence CVE CVE-2021-46964 https://www.cve.org/CVERecord?id=CVE-2021-46964 Référence CVE CVE-2021-46966 https://www.cve.org/CVERecord?id=CVE-2021-46966 Référence CVE CVE-2021-46975 https://www.cve.org/CVERecord?id=CVE-2021-46975 Référence CVE CVE-2021-46981 https://www.cve.org/CVERecord?id=CVE-2021-46981 Référence CVE CVE-2021-46988 https://www.cve.org/CVERecord?id=

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

742-1 du 19 avril 2024 https://ubuntu.com/security/notices/USN-6742-1 Bulletin de sécurité Ubuntu USN-6742-2 du 23 avril 2024 https://ubuntu.com/security/notices/USN-6742-2 Bulletin de sécurité Ubuntu USN-6743-1 du 19 avril 2024 https://ubuntu.com/security/notices/USN-6743-1 Bulletin de sécurité Ubuntu USN-6743-2 du 22 avril 2024 https://ubuntu.com/security/notices/USN-6743-2 Bulletin de sécurité Ubuntu USN-6743-3 du 24 avril 2024 https://ubuntu.com/security/notices/USN-6743-3 Référence CVE CVE-2019-25162 https://www.cve.org/CVERecord?id=CVE-2019-25162 Référence CVE CVE-2021-46936 https://www.cve.org/CVERecord?id=CVE-2021-46936 Référence CVE CVE-2021-46955 https://www.cve.org/CVERecord?id=CVE-2021-46955 Référence CVE CVE-2021-46966 https://www.cve.org/CVERecord?id=CVE-2021-46966 Référence CVE CVE-2021-46990 https://www.cve.org/CVERecord?id=CVE-2021-46990 Référence CVE CVE-2022-20422 https://www.cve.org/CVERecord?id=CVE-2022-20422 Référence CVE CVE-2023-1382 https://www.cve.org/CVERecord?id=CVE-2023-1382 Référence CVE CVE-2023-1838 https://www.cve.org/CVERecord?id=CVE-2023-1838 Référence CVE CVE-2023-1998 https://www.cve.org/CVERecord?id=CVE-2023-1998 Référence CVE CVE-2023-24023 https://www.cve.org/CVERecord?id=CVE-2023-24023 Référence CVE CVE-2023-51043 https://www.cve.org/CVERecord?id=CVE-20

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-021334Linux の Linux Kernel における境界外読み取りに関する脆弱性

Linux の Linux Kernel には、境界外読み取りに関する脆弱性が存在します。

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
Fixed
Linux: < 4.16, 4.4.269 ≤ 4.4.*, 4.9.269 ≤ 4.9.*, 4.14.233 ≤ 4.14.*, 4.19.191 ≤ 4.19.*, 5.4.118 ≤ 5.4.*, 5.10.36 ≤ 5.10.*, 5.11.20 ≤ 5.11.*, 5.12.3 ≤ 5.12.*, 5.13 ≤ *
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 27 Feb 2024 · Last source change 5 Aug 2026, 08:45 UTC · CWE-125 · Out-of-bounds Read

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-2021-33603
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

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-2021-33603↗Vendor CSAF · SUSE Product Security Team↗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-2021-46955 · cve.blacktree.nl