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

RDMA/rxe: Return CQE error if invalid lkey was supplied

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. 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 severityMediumOperational priority:Low, lowered one band.downgradedsince 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.23% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • 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: No default targetRemediation target: Normal maintenance

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.14.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.14.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.14.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.14.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
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-33724

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. 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: RDMA/rxe: Return CQE error if invalid lkey was supplied RXE is missing update of WQE status in LOCAL_WRITE failures. This caused the following kernel panic if someone sent an atomic operation with an explicitly wrong lkey. [leonro@vm ~]$ mkt test test_atomic_invalid_lkey (tests.test_atomic.AtomicTest) ... WARNING: CPU: 5 PID: 263 at drivers/infiniband/sw/rxe/rxe_comp.c:740 rxe_completer+0x1a6d/0x2e30 [rdma_rxe] Modules linked in: crc32_generic rdma_rxe ip6_udp_tunnel udp_tunnel rdma_ucm rdma_cm ib_umad ib_ipoib iw_cm ib_cm mlx5_ib ib_uverbs ib_core mlx5_core ptp pps_core CPU: 5 PID: 263 Comm: python3 Not tainted 5.13.0-rc1+ #2936 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:rxe_completer+0x1a6d/0x2e30 [rdma_rxe] Code: 03 0f 8e 65 0e 00 00 3b 93 10 06 00 00 0f 84 82 0a 00 00 4c 89 ff 4c 89 44 24 38 e8 2d 74 a9 e1 4c 8b 44 24 38 e9 1c f5 ff ff <0f> 0b e9 0c e8 ff ff b8 05 00 00 00 41 bf 05 00 00 00 e9 ab e7 ff RSP: 0018:ffff8880158af090 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff888016a78000 RCX: ffffffffa0cf1652 RDX: 1ffff9200004b442 RSI: 0000000000000004 RDI: ffffc9000025a210 RBP: dffffc0000000000 R08: 00000000ffffffea R09: ffff88801617740b R10: ffffed1002c2ee81 R11: 0000000000000007 R12: ffff88800f3b63e8 R13: ffff888016a78008 R14: ffffc9000025a180 R15: 000000000000000c FS: 00007f88b622a740(0000) GS:ffff88806d540000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f88b5a1fa10 CR3: 000000000d848004 CR4: 0000000000370ea0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: rxe_do_task+0x130/0x230 [rdma_rxe] rxe_rcv+0xb11/0x1df0 [rdma_rxe] rxe_loopback+0x157/0x1e0 [rdma_rxe] rxe_responder+0x5532/0x7620 [rdma_rxe] rxe_do_task+0x130/0x230 [rdma_rxe] rxe_rcv+0x9c8/0x1df0 [rdma_rxe] rxe_loopback+0x157/0x1e0 [rdma_rxe] rxe_requester+0x1efd/0x58c0 [rdma_rxe] rxe_do_task+0x130/0x230 [rdma_rxe] rxe_post_send+0x998/0x1860 [rdma_rxe] ib_uverbs_post_send+0xd5f/0x1220 [ib_uverbs] ib_uverbs_write+0x847/0xc80 [ib_uverbs] vfs_write+0x1c5/0x840 ksys_write+0x176/0x1d0 do_syscall_64+0x3f/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae

What

In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Return CQE error if invalid lkey was supplied RXE is missing update of WQE status in LOCAL_WRITE failures. This caused the following kernel panic if someone sent an atomic operation with an explicitly wrong lkey. [leonro@vm ~]$ mkt test test_atomic_invalid_lkey (tests.test_atomic.AtomicTest) ... WARNING: CPU: 5 PID: 263 at drivers/infiniband/sw/rxe/rxe_comp.c:740 rxe_completer+0x1a6d/0x2e30 [rdma_rxe] Modules linked in: crc32_generic rdma_rxe ip6_udp_tunnel udp_tunnel rdma_ucm rdma_cm ib_umad ib_ipoib iw_cm ib_cm mlx5_ib ib_uverbs ib_core mlx5_core ptp pps_core CPU: 5 PID: 263 Comm: python3 Not tainted 5.13.0-rc1+ #2936 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:rxe_completer+0x1a6d/0x2e30 [rdma_rxe] Code: 03 0f 8e 65 0e 00 00 3b 93 10 06 00 00 0f 84 82 0a 00 00 4c 89 ff 4c 89 44 24 38 e8 2d 74 a9 e1 4c 8b 44 24 38 e9 1c f5 ff ff <0f> 0b e9 0c e8 ff ff b8 05 00 00 00 41 bf 05 00 00 00 e9 ab e7 ff RSP: 0018:ffff8880158af090 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff888016a78000 RCX: ffffffffa0cf1652 RDX: 1ffff9200004b442 RSI: 0000000000000004 RDI: ffffc9000025a210 RBP: dffffc0000000000 R08: 00000000ffffffea R09: ffff88801617740b R10: ffffed1002c2ee81 R11: 0000000000000007 R12: ffff88800f3b63e8 R13: ffff888016a78008 R14: ffffc9000025a180 R15: 000000000000000c FS: 00007f88b622a740(0000) GS:ffff88806d540000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f88b5a1fa10 CR3: 000000000d848004 CR4: 0000000000370ea0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: rxe_do_task+0x130/0x230 [rdma_rxe] rxe_rcv+0xb11/0x1df0 [rdma_rxe] rxe_loopback+0x157/0x1e0 [rdma_rxe] rxe_responder+0x5532/0x7620 [rdma_rxe] rxe_do_task+0x130/0x230 [rdma_rxe] rxe_rcv+0x9c8/0x1df0 [rdma_rxe] rxe_loopback+0x157/0x1e0 [rdma_rxe] rxe_requester+0x1efd/0x58c0 [rdma_rxe] rxe_do_task+0x130/0x230 [rdma_rxe] rxe_post_send+0x998/0x1860 [rdma_rxe] ib_uverbs_post_send+0xd5f/0x1220 [ib_uverbs] ib_uverbs_write+0x847/0xc80 [ib_uverbs] vfs_write+0x1c5/0x840 ksys_write+0x176/0x1d0 do_syscall_64+0x3f/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae

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 local access may attempt exploitation with low privileges. 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: RDMA/rxe: Return CQE error if invalid lkey was supplied RXE is missing update of WQE status in LOCAL_WRITE failures. This caused the following kernel panic if someone sent an atomic operation with an explicitly wrong lkey. [leonro@vm ~]$ mkt test test_atomic_invalid_lkey (tests.test_atomic.AtomicTest) ... WARNING: CPU: 5 PID: 263 at drivers/infiniband/sw/rxe/rxe_comp.c:740 rxe_completer+0x1a6d/0x2e30 [rdma_rxe] Modules linked in: crc32_generic rdma_rxe ip6_udp_tunnel udp_tunnel rdma_ucm rdma_cm ib_umad ib_ipoib iw_cm ib_cm mlx5_ib ib_uverbs ib_core mlx5_core ptp pps_core CPU: 5 PID: 263 Comm: python3 Not tainted 5.13.0-rc1+ #2936 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:rxe_completer+0x1a6d/0x2e30 [rdma_rxe] Code: 03 0f 8e 65 0e 00 00 3b 93 10 06 00 00 0f 84 82 0a 00 00 4c 89 ff 4c 89 44 24 38 e8 2d 74 a9 e1 4c 8b 44 24 38 e9 1c f5 ff ff <0f> 0b e9 0c e8 ff ff b8 05 00 00 00 41 bf 05 00 00 00 e9 ab e7 ff RSP: 0018:ffff8880158af090 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff888016a78000 RCX: ffffffffa0cf1652 RDX: 1ffff9200004b442 RSI: 0000000000000004 RDI: ffffc9000025a210 RBP: dffffc0000000000 R08: 00000000ffffffea R09: ffff88801617740b R10: ffffed1002c2ee81 R11: 0000000000000007 R12: ffff88800f3b63e8 R13: ffff888016a78008 R14: ffffc9000025a180 R15: 000000000000000c FS: 00007f88b622a740(0000) GS:ffff88806d540000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f88b5a1fa10 CR3: 000000000d848004 CR4: 0000000000370ea0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: rxe_do_task+0x130/0x230 [rdma_rxe] rxe_rcv+0xb11/0x1df0 [rdma_rxe] rxe_loopback+0x157/0x1e0 [rdma_rxe] rxe_responder+0x5532/0x7620 [rdma_rxe] rxe_do_task+0x130/0x230 [rdma_rxe] rxe_rcv+0x9c8/0x1df0 [rdma_rxe] rxe_loopback+0x157/0x1e0 [rdma_rxe] rxe_requester+0x1efd/0x58c0 [rdma_rxe] rxe_do_task+0x130/0x230 [rdma_rxe] rxe_post_send+0x998/0x1860 [rdma_rxe] ib_uverbs_post_send+0xd5f/0x1220 [ib_uverbs] ib_uverbs_write+0x847/0xc80 [ib_uverbs] vfs_write+0x1c5/0x840 ksys_write+0x176/0x1d0 do_syscall_64+0x3f/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae

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 local access may attempt exploitation with low privileges. 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
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
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:L/AC:L/PR:L/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.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level 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
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-0534Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen oder einen nicht spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240306Security Bulletin 06 Mar 2024

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

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

i de service. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Debian LTS DLA-4327-1 du 13 octobre 2025 https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html Bulletin de sécurité Debian LTS DLA-4328-1 du 13 octobre 2025 https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html Référence CVE CVE-2021-46987 https://www.cve.org/CVERecord?id=CVE-2021-46987 Référence CVE CVE-2021-47037 https://www.cve.org/CVERecord?id=CVE-2021-47037 Référence CVE CVE-2021-47070 https://www.cve.org/CVERecord?id=CVE-2021-47070 Référence CVE CVE-2021-47076 https://www.cve.org/CVERecord?id=CVE-2021-47076 Référence CVE CVE-2021-47183 https://www.cve.org/CVERecord?id=CVE-2021-47183 Référence CVE CVE-2021-47193 https://www.cve.org/CVERecord?id=CVE-2021-47193 Référence CVE CVE-2021-47412 https://www.cve.org/CVERecord?id=CVE-2021-47412 Référence CVE CVE-2021-47421 https://www.cve.org/CVERecord?id=CVE-2021-47421 Référence CVE CVE-2021-47455 https://www.cve.org/CVERecord?id=CVE-2021-47455 Référence CVE CVE-2021-47498 https://www.cve.org/CVERecord?id=CVE-2021-47498 Référence CVE CVE-2022-21546 https://www.cve.org/CVERecord?id=CVE-2022-21546 Référence CVE CVE-2022-49063 https://www.cve.org/CVERecord?id=

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

de provoquer une élévation de privilèges, une atteinte à la confidentialité des données et un déni de service. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Ubuntu USN-7169-5 du 10 janvier 2025 https://ubuntu.com/security/notices/USN-7169-5 Bulletin de sécurité Ubuntu USN-7195-2 du 14 janvier 2025 https://ubuntu.com/security/notices/USN-7195-2 Bulletin de sécurité Ubuntu USN-7173-3 du 15 janvier 2025 https://ubuntu.com/security/notices/USN-7173-3 Référence CVE CVE-2021-47001 https://www.cve.org/CVERecord?id=CVE-2021-47001 Référence CVE CVE-2021-47076 https://www.cve.org/CVERecord?id=CVE-2021-47076 Référence CVE CVE-2021-47101 https://www.cve.org/CVERecord?id=CVE-2021-47101 Référence CVE CVE-2021-47501 https://www.cve.org/CVERecord?id=CVE-2021-47501 Référence CVE CVE-2022-38096 https://www.cve.org/CVERecord?id=CVE-2022-38096 Référence CVE CVE-2022-48733 https://www.cve.org/CVERecord?id=CVE-2022-48733 Référence CVE CVE-2022-48938 https://www.cve.org/CVERecord?id=CVE-2022-48938 Référence CVE CVE-2022-48943 https://www.cve.org/CVERecord?id=CVE-2022-48943 Référence CVE CVE-2023-52488 https://www.cve.org/CVERecord?id=CVE-2023-52488 Référence CVE CVE-2023-52497 https://www.cve.org/CVERecord?id=

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

s/USN-7186-2 Bulletin de sécurité Ubuntu USN-7194-1 du 09 janvier 2025 https://ubuntu.com/security/notices/USN-7194-1 Bulletin de sécurité Ubuntu USN-7195-1 du 09 janvier 2025 https://ubuntu.com/security/notices/USN-7195-1 Bulletin de sécurité Ubuntu USN-7196-1 du 09 janvier 2025 https://ubuntu.com/security/notices/USN-7196-1 Référence CVE CVE-2020-12351 https://www.cve.org/CVERecord?id=CVE-2020-12351 Référence CVE CVE-2020-12352 https://www.cve.org/CVERecord?id=CVE-2020-12352 Référence CVE CVE-2020-24490 https://www.cve.org/CVERecord?id=CVE-2020-24490 Référence CVE CVE-2021-47001 https://www.cve.org/CVERecord?id=CVE-2021-47001 Référence CVE CVE-2021-47076 https://www.cve.org/CVERecord?id=CVE-2021-47076 Référence CVE CVE-2021-47082 https://www.cve.org/CVERecord?id=CVE-2021-47082 Référence CVE CVE-2021-47086 https://www.cve.org/CVERecord?id=CVE-2021-47086 Référence CVE CVE-2021-47101 https://www.cve.org/CVERecord?id=CVE-2021-47101 Référence CVE CVE-2021-47118 https://www.cve.org/CVERecord?id=CVE-2021-47118 Référence CVE CVE-2021-47501 https://www.cve.org/CVERecord?id=CVE-2021-47501 Référence CVE CVE-2022-36402 https://www.cve.org/CVERecord?id=CVE-2022-36402 Référence CVE CVE-2022-38096 https://www.cve.org/CVERecord?id=CVE-2022-38096 Référence CVE CVE-2022-48666 https://www.cve.org/CVERecord?id=

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

SN-7159-4 Bulletin de sécurité Ubuntu USN-7166-3 du 20 décembre 2024 https://ubuntu.com/security/notices/USN-7166-3 Bulletin de sécurité Ubuntu USN-7173-2 du 20 décembre 2024 https://ubuntu.com/security/notices/USN-7173-2 Bulletin de sécurité Ubuntu USN-7179-1 du 20 décembre 2024 https://ubuntu.com/security/notices/USN-7179-1 Référence CVE CVE-2020-12351 https://www.cve.org/CVERecord?id=CVE-2020-12351 Référence CVE CVE-2020-12352 https://www.cve.org/CVERecord?id=CVE-2020-12352 Référence CVE CVE-2020-24490 https://www.cve.org/CVERecord?id=CVE-2020-24490 Référence CVE CVE-2021-47001 https://www.cve.org/CVERecord?id=CVE-2021-47001 Référence CVE CVE-2021-47076 https://www.cve.org/CVERecord?id=CVE-2021-47076 Référence CVE CVE-2021-47101 https://www.cve.org/CVERecord?id=CVE-2021-47101 Référence CVE CVE-2021-47501 https://www.cve.org/CVERecord?id=CVE-2021-47501 Référence CVE CVE-2022-38096 https://www.cve.org/CVERecord?id=CVE-2022-38096 Référence CVE CVE-2022-48733 https://www.cve.org/CVERecord?id=CVE-2022-48733 Référence CVE CVE-2022-48938 https://www.cve.org/CVERecord?id=CVE-2022-48938 Référence CVE CVE-2022-48943 https://www.cve.org/CVERecord?id=CVE-2022-48943 Référence CVE CVE-2023-52488 https://www.cve.org/CVERecord?id=CVE-2023-52488 Référence CVE CVE-2023-52497 https://www.cve.org/CVERecord?id=

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

/security/notices/USN-7167-1 Bulletin de sécurité Ubuntu USN-7169-1 du 17 décembre 2024 https://ubuntu.com/security/notices/USN-7169-1 Bulletin de sécurité Ubuntu USN-7170-1 du 17 décembre 2024 https://ubuntu.com/security/notices/USN-7170-1 Bulletin de sécurité Ubuntu USN-7173-1 du 17 décembre 2024 https://ubuntu.com/security/notices/USN-7173-1 Bulletin de sécurité Ubuntu USN-7169-2 du 18 décembre 2024 https://ubuntu.com/security/notices/USN-7169-2 Bulletin de sécurité Ubuntu LSN-0108-1 du 19 décembre 2024 https://ubuntu.com/security/notices/LSN-0108-1 Référence CVE CVE-2021-47001 https://www.cve.org/CVERecord?id=CVE-2021-47001 Référence CVE CVE-2021-47076 https://www.cve.org/CVERecord?id=CVE-2021-47076 Référence CVE CVE-2021-47101 https://www.cve.org/CVERecord?id=CVE-2021-47101 Référence CVE CVE-2021-47501 https://www.cve.org/CVERecord?id=CVE-2021-47501 Référence CVE CVE-2022-38096 https://www.cve.org/CVERecord?id=CVE-2022-38096 Référence CVE CVE-2022-48733 https://www.cve.org/CVERecord?id=CVE-2022-48733 Référence CVE CVE-2022-48938 https://www.cve.org/CVERecord?id=CVE-2022-48938 Référence CVE CVE-2022-48943 https://www.cve.org/CVERecord?id=CVE-2022-48943 Référence CVE CVE-2023-52488 https://www.cve.org/CVERecord?id=CVE-2023-52488 Référence CVE CVE-2023-52497 https://www.cve.org/CVERecord?id=

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

/security/notices/USN-7144-1 Bulletin de sécurité Ubuntu USN-7148-1 du 10 décembre 2024 https://ubuntu.com/security/notices/USN-7148-1 Bulletin de sécurité Ubuntu USN-7154-1 du 12 décembre 2024 https://ubuntu.com/security/notices/USN-7154-1 Bulletin de sécurité Ubuntu USN-7155-1 du 12 décembre 2024 https://ubuntu.com/security/notices/USN-7155-1 Bulletin de sécurité Ubuntu USN-7156-1 du 12 décembre 2024 https://ubuntu.com/security/notices/USN-7156-1 Bulletin de sécurité Ubuntu USN-7159-1 du 12 décembre 2024 https://ubuntu.com/security/notices/USN-7159-1 Référence CVE CVE-2021-47055 https://www.cve.org/CVERecord?id=CVE-2021-47055 Référence CVE CVE-2021-47076 https://www.cve.org/CVERecord?id=CVE-2021-47076 Référence CVE CVE-2021-47501 https://www.cve.org/CVERecord?id=CVE-2021-47501 Référence CVE CVE-2022-24448 https://www.cve.org/CVERecord?id=CVE-2022-24448 Référence CVE CVE-2022-48666 https://www.cve.org/CVERecord?id=CVE-2022-48666 Référence CVE CVE-2022-48733 https://www.cve.org/CVERecord?id=CVE-2022-48733 Référence CVE CVE-2022-48938 https://www.cve.org/CVERecord?id=CVE-2022-48938 Référence CVE CVE-2022-48943 https://www.cve.org/CVERecord?id=CVE-2022-48943 Référence CVE CVE-2023-52488 https://www.cve.org/CVERecord?id=CVE-2023-52488 Référence CVE CVE-2023-52497 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2021-46991 Référence CVE CVE-2021-46992 https://www.cve.org/CVERecord?id=CVE-2021-46992 Référence CVE CVE-2021-47005 https://www.cve.org/CVERecord?id=CVE-2021-47005 Référence CVE CVE-2021-47012 https://www.cve.org/CVERecord?id=CVE-2021-47012 Référence CVE CVE-2021-47013 https://www.cve.org/CVERecord?id=CVE-2021-47013 Référence CVE CVE-2021-47054 https://www.cve.org/CVERecord?id=CVE-2021-47054 Référence CVE CVE-2021-47060 https://www.cve.org/CVERecord?id=CVE-2021-47060 Référence CVE CVE-2021-47061 https://www.cve.org/CVERecord?id=CVE-2021-47061 Référence CVE CVE-2021-47069 https://www.cve.org/CVERecord?id=CVE-2021-47069 Référence CVE CVE-2021-47076 https://www.cve.org/CVERecord?id=CVE-2021-47076 Référence CVE CVE-2021-47077 https://www.cve.org/CVERecord?id=CVE-2021-47077 Référence CVE CVE-2021-47078 https://www.cve.org/CVERecord?id=CVE-2021-47078 Référence CVE CVE-2021-47083 https://www.cve.org/CVERecord?id=CVE-2021-47083 Référence CVE CVE-2022-20154 https://www.cve.org/CVERecord?id=CVE-2022-20154 Référence CVE CVE-2022-48627 https://www.cve.org/CVERecord?id=CVE-2022-48627 Référence CVE CVE-2023-0461 https://www.cve.org/CVERecord?id=CVE-2023-0461 Référence CVE CVE-2023-28746 https://www.cve.org/CVERecord?id=CVE-2023-28746 Référence CVE CVE-2023-35827 https://www.cve.org/CVERecord?id=CV

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

d?id=CVE-2021-46974 Référence CVE CVE-2021-46989 https://www.cve.org/CVERecord?id=CVE-2021-46989 Référence CVE CVE-2021-47005 https://www.cve.org/CVERecord?id=CVE-2021-47005 Référence CVE CVE-2021-47012 https://www.cve.org/CVERecord?id=CVE-2021-47012 Référence CVE CVE-2021-47013 https://www.cve.org/CVERecord?id=CVE-2021-47013 Référence CVE CVE-2021-47054 https://www.cve.org/CVERecord?id=CVE-2021-47054 Référence CVE CVE-2021-47060 https://www.cve.org/CVERecord?id=CVE-2021-47060 Référence CVE CVE-2021-47061 https://www.cve.org/CVERecord?id=CVE-2021-47061 Référence CVE CVE-2021-47069 https://www.cve.org/CVERecord?id=CVE-2021-47069 Référence CVE CVE-2021-47076 https://www.cve.org/CVERecord?id=CVE-2021-47076 Référence CVE CVE-2021-47078 https://www.cve.org/CVERecord?id=CVE-2021-47078 Référence CVE CVE-2021-47083 https://www.cve.org/CVERecord?id=CVE-2021-47083 Référence CVE CVE-2022-20154 https://www.cve.org/CVERecord?id=CVE-2022-20154 Référence CVE CVE-2022-48627 https://www.cve.org/CVERecord?id=CVE-2022-48627 Référence CVE CVE-2022-48628 https://www.cve.org/CVERecord?id=CVE-2022-48628 Référence CVE CVE-2023-28746 https://www.cve.org/CVERecord?id=CVE-2023-28746 Référence CVE CVE-2023-35827 https://www.cve.org/CVERecord?id=CVE-2023-35827 Référence CVE CVE-2023-46343 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-021396Linux の 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
Linux: 8700e3e7c4857d28ebaa824509934556da0b3e76 < a81e72d49b0648f68ab201163dbfc7841056d7a2, 8700e3e7c4857d28ebaa824509934556da0b3e76 < abe31d25facdb9109fe2cf69890748295291570c, 8700e3e7c4857d28ebaa824509934556da0b3e76 < dc07628bd2bbc1da768e265192c28ebd301f509d, 4.8
Fixed
Linux: < 4.8, 5.10.241 ≤ 5.10.*, 5.12.7 ≤ 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. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 1 Mar 2024 · Last source change 11 May 2026, 13:47 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
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-33724
Product sourceCNA
Remediation sourceCVE/CNA references
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-2021-33724↗Patch or update reference↗Patch or update reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2021-47076 · cve.blacktree.nl