BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2022-48830High confidence

can: isotp: fix potential CAN frame reception race in isotp_rcv()

Linux · Linux

8.8HighCVSS 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.

1 package state
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 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 8 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.

1 current
CVE-2022-48830 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: can: isotp: fix potential CAN frame reception race in isotp_rcv()
22 known affected

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

  • kernel-rt as a component of Red Hat Enterprise Linux 9
  • kernel-rt-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel-matched as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-partner as a component of Red Hat Enterprise Linux 9
Summary
A potential CAN frame reception race flaw was found in isotp_rcv() in the Linux kernel. This vulnerability may lead to a crash.
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.
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-2022-53709

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 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: can: isotp: fix potential CAN frame reception race in isotp_rcv() When receiving a CAN frame the current code logic does not consider concurrently receiving processes which do not show up in real world usage. Ziyang Xuan writes: The following syz problem is one of the scenarios. so->rx.len is changed by isotp_rcv_ff() during isotp_rcv_cf(), so->rx.len equals 0 before alloc_skb() and equals 4096 after alloc_skb(). That will trigger skb_over_panic() in skb_put(). ======================================================= CPU: 1 PID: 19 Comm: ksoftirqd/1 Not tainted 5.16.0-rc8-syzkaller #0 RIP: 0010:skb_panic+0x16c/0x16e net/core/skbuff.c:113 Call Trace: <TASK> skb_over_panic net/core/skbuff.c:118 [inline] skb_put.cold+0x24/0x24 net/core/skbuff.c:1990 isotp_rcv_cf net/can/isotp.c:570 [inline] isotp_rcv+0xa38/0x1e30 net/can/isotp.c:668 deliver net/can/af_can.c:574 [inline] can_rcv_filter+0x445/0x8d0 net/can/af_can.c:635 can_receive+0x31d/0x580 net/can/af_can.c:665 can_rcv+0x120/0x1c0 net/can/af_can.c:696 __netif_receive_skb_one_core+0x114/0x180 net/core/dev.c:5465 __netif_receive_skb+0x24/0x1b0 net/core/dev.c:5579 Therefore we make sure the state changes and data structures stay consistent at CAN frame reception time by adding a spin_lock in isotp_rcv(). This fixes the issue reported by syzkaller but does not affect real world operation.

What

In the Linux kernel, the following vulnerability has been resolved: can: isotp: fix potential CAN frame reception race in isotp_rcv() When receiving a CAN frame the current code logic does not consider concurrently receiving processes which do not show up in real world usage. Ziyang Xuan writes: The following syz problem is one of the scenarios. so->rx.len is changed by isotp_rcv_ff() during isotp_rcv_cf(), so->rx.len equals 0 before alloc_skb() and equals 4096 after alloc_skb(). That will trigger skb_over_panic() in skb_put(). ======================================================= CPU: 1 PID: 19 Comm: ksoftirqd/1 Not tainted 5.16.0-rc8-syzkaller #0 RIP: 0010:skb_panic+0x16c/0x16e net/core/skbuff.c:113 Call Trace: <TASK> skb_over_panic net/core/skbuff.c:118 [inline] skb_put.cold+0x24/0x24 net/core/skbuff.c:1990 isotp_rcv_cf net/can/isotp.c:570 [inline] isotp_rcv+0xa38/0x1e30 net/can/isotp.c:668 deliver net/can/af_can.c:574 [inline] can_rcv_filter+0x445/0x8d0 net/can/af_can.c:635 can_receive+0x31d/0x580 net/can/af_can.c:665 can_rcv+0x120/0x1c0 net/can/af_can.c:696 __netif_receive_skb_one_core+0x114/0x180 net/core/dev.c:5465 __netif_receive_skb+0x24/0x1b0 net/core/dev.c:5579 Therefore we make sure the state changes and data structures stay consistent at CAN frame reception time by adding a spin_lock in isotp_rcv(). This fixes the issue reported by syzkaller but does not affect real world operation.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

How

An attacker operating through an adjacent network 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: can: isotp: fix potential CAN frame reception race in isotp_rcv() When receiving a CAN frame the current code logic does not consider concurrently receiving processes which do not show up in real world usage. Ziyang Xuan writes: The following syz problem is one of the scenarios. so->rx.len is changed by isotp_rcv_ff() during isotp_rcv_cf(), so->rx.len equals 0 before alloc_skb() and equals 4096 after alloc_skb(). That will trigger skb_over_panic() in skb_put(). ======================================================= CPU: 1 PID: 19 Comm: ksoftirqd/1 Not tainted 5.16.0-rc8-syzkaller #0 RIP: 0010:skb_panic+0x16c/0x16e net/core/skbuff.c:113 Call Trace: <TASK> skb_over_panic net/core/skbuff.c:118 [inline] skb_put.cold+0x24/0x24 net/core/skbuff.c:1990 isotp_rcv_cf net/can/isotp.c:570 [inline] isotp_rcv+0xa38/0x1e30 net/can/isotp.c:668 deliver net/can/af_can.c:574 [inline] can_rcv_filter+0x445/0x8d0 net/can/af_can.c:635 can_receive+0x31d/0x580 net/can/af_can.c:665 can_rcv+0x120/0x1c0 net/can/af_can.c:696 __netif_receive_skb_one_core+0x114/0x180 net/core/dev.c:5465 __netif_receive_skb+0x24/0x1b0 net/core/dev.c:5579 Therefore we make sure the state changes and data structures stay consistent at CAN frame reception time by adding a spin_lock in isotp_rcv(). This fixes the issue reported by syzkaller but does not affect real world operation.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

How

An attacker operating through an adjacent network 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
an adjacent network → Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Adjacent
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-362 ↗

CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'). The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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

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

Official authority intelligence

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

BSI · German · WID-SEC-W-2026-2253IBM Security Verify Access: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Security Verify Access ausnutzen, um erweiterte Berechtigungen zu erlangen, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, sensible Informationen offenzulegen und andere, nicht näher bezeichnete Angriffe durchzuführen.

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

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

Official advisory
CERT-FR · French · CERTFR-2025-AVI-1057Multiples vulnérabilités dans les produits VMware

d?id=CVE-2022-48810 Référence CVE CVE-2022-48812 https://www.cve.org/CVERecord?id=CVE-2022-48812 Référence CVE CVE-2022-48813 https://www.cve.org/CVERecord?id=CVE-2022-48813 Référence CVE CVE-2022-48815 https://www.cve.org/CVERecord?id=CVE-2022-48815 Référence CVE CVE-2022-48817 https://www.cve.org/CVERecord?id=CVE-2022-48817 Référence CVE CVE-2022-48818 https://www.cve.org/CVERecord?id=CVE-2022-48818 Référence CVE CVE-2022-48819 https://www.cve.org/CVERecord?id=CVE-2022-48819 Référence CVE CVE-2022-48823 https://www.cve.org/CVERecord?id=CVE-2022-48823 Référence CVE CVE-2022-48825 https://www.cve.org/CVERecord?id=CVE-2022-48825 Référence CVE CVE-2022-48830 https://www.cve.org/CVERecord?id=CVE-2022-48830 Référence CVE CVE-2022-48831 https://www.cve.org/CVERecord?id=CVE-2022-48831 Référence CVE CVE-2022-48832 https://www.cve.org/CVERecord?id=CVE-2022-48832 Référence CVE CVE-2022-48834 https://www.cve.org/CVERecord?id=CVE-2022-48834 Référence CVE CVE-2022-48835 https://www.cve.org/CVERecord?id=CVE-2022-48835 Référence CVE CVE-2022-48836 https://www.cve.org/CVERecord?id=CVE-2022-48836 Référence CVE CVE-2022-48837 https://www.cve.org/CVERecord?id=CVE-2022-48837 Référence CVE CVE-2022-48839 https://www.cve.org/CVERecord?id=CVE-2022-48839 Référence CVE CVE-2022-48840 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-48821 Référence CVE CVE-2022-48822 https://www.cve.org/CVERecord?id=CVE-2022-48822 Référence CVE CVE-2022-48823 https://www.cve.org/CVERecord?id=CVE-2022-48823 Référence CVE CVE-2022-48824 https://www.cve.org/CVERecord?id=CVE-2022-48824 Référence CVE CVE-2022-48825 https://www.cve.org/CVERecord?id=CVE-2022-48825 Référence CVE CVE-2022-48826 https://www.cve.org/CVERecord?id=CVE-2022-48826 Référence CVE CVE-2022-48827 https://www.cve.org/CVERecord?id=CVE-2022-48827 Référence CVE CVE-2022-48828 https://www.cve.org/CVERecord?id=CVE-2022-48828 Référence CVE CVE-2022-48829 https://www.cve.org/CVERecord?id=CVE-2022-48829 Référence CVE CVE-2022-48830 https://www.cve.org/CVERecord?id=CVE-2022-48830 Référence CVE CVE-2022-48831 https://www.cve.org/CVERecord?id=CVE-2022-48831 Référence CVE CVE-2022-48834 https://www.cve.org/CVERecord?id=CVE-2022-48834 Référence CVE CVE-2022-48835 https://www.cve.org/CVERecord?id=CVE-2022-48835 Référence CVE CVE-2022-48836 https://www.cve.org/CVERecord?id=CVE-2022-48836 Référence CVE CVE-2022-48837 https://www.cve.org/CVERecord?id=CVE-2022-48837 Référence CVE CVE-2022-48838 https://www.cve.org/CVERecord?id=CVE-2022-48838 Référence CVE CVE-2022-48839 https://www.cve.org/CVERecord?id=CVE-2022-48839 Référence CVE CVE-2022-48840 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-48821 Référence CVE CVE-2022-48822 https://www.cve.org/CVERecord?id=CVE-2022-48822 Référence CVE CVE-2022-48823 https://www.cve.org/CVERecord?id=CVE-2022-48823 Référence CVE CVE-2022-48824 https://www.cve.org/CVERecord?id=CVE-2022-48824 Référence CVE CVE-2022-48825 https://www.cve.org/CVERecord?id=CVE-2022-48825 Référence CVE CVE-2022-48826 https://www.cve.org/CVERecord?id=CVE-2022-48826 Référence CVE CVE-2022-48827 https://www.cve.org/CVERecord?id=CVE-2022-48827 Référence CVE CVE-2022-48828 https://www.cve.org/CVERecord?id=CVE-2022-48828 Référence CVE CVE-2022-48829 https://www.cve.org/CVERecord?id=CVE-2022-48829 Référence CVE CVE-2022-48830 https://www.cve.org/CVERecord?id=CVE-2022-48830 Référence CVE CVE-2022-48831 https://www.cve.org/CVERecord?id=CVE-2022-48831 Référence CVE CVE-2022-48834 https://www.cve.org/CVERecord?id=CVE-2022-48834 Référence CVE CVE-2022-48835 https://www.cve.org/CVERecord?id=CVE-2022-48835 Référence CVE CVE-2022-48836 https://www.cve.org/CVERecord?id=CVE-2022-48836 Référence CVE CVE-2022-48837 https://www.cve.org/CVERecord?id=CVE-2022-48837 Référence CVE CVE-2022-48838 https://www.cve.org/CVERecord?id=CVE-2022-48838 Référence CVE CVE-2022-48839 https://www.cve.org/CVERecord?id=CVE-2022-48839 Référence CVE CVE-2022-48840 https://www.cve.org/CVERecord?id=

Official advisory
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
kernel-rt as a component of Red Hat Enterprise Linux 9; kernel-rt-core as a component of Red Hat Enterprise Linux 9; kernel-rt-debug as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-core as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules-core as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules-partner as a component of Red Hat Enterprise Linux 9; kernel-rt-devel as a component of Red Hat Enterprise Linux 9; kernel-rt-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-rt-kvm as a component of Red Hat Enterprise Linux 9; kernel-rt-modules as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-core as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-extra as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-internal as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-partner as a component of Red Hat Enterprise Linux 9; kernel-rt-selftests-internal as a component of Red Hat Enterprise Linux 9; kernel-rt.src as a component of Red Hat Enterprise Linux 9
Fixed
kernel-64k-debug-debuginfo-0:5.14.0-611.5.1.el9_7.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-debug-devel-0:5.14.0-611.5.1.el9_7.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-debug-devel-matched-0:5.14.0-611.5.1.el9_7.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-debuginfo-0:5.14.0-611.5.1.el9_7.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-devel-0:5.14.0-611.5.1.el9_7.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-64k-devel-matched-0:5.14.0-611.5.1.el9_7.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-debuginfo-0:5.14.0-611.5.1.el9_7.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-debuginfo-0:5.14.0-611.5.1.el9_7.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-debuginfo-0:5.14.0-611.5.1.el9_7.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-debuginfo-0:5.14.0-611.5.1.el9_7.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-0:5.14.0-611.5.1.el9_7.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-0:5.14.0-611.5.1.el9_7.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-0:5.14.0-611.5.1.el9_7.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-0:5.14.0-611.5.1.el9_7.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-matched-0:5.14.0-611.5.1.el9_7.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-matched-0:5.14.0-611.5.1.el9_7.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-matched-0:5.14.0-611.5.1.el9_7.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debug-devel-matched-0:5.14.0-611.5.1.el9_7.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-0:5.14.0-611.5.1.el9_7.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-0:5.14.0-611.5.1.el9_7.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-0:5.14.0-611.5.1.el9_7.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-0:5.14.0-611.5.1.el9_7.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-common-aarch64-0:5.14.0-611.5.1.el9_7.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-common-ppc64le-0:5.14.0-611.5.1.el9_7.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-common-s390x-0:5.14.0-611.5.1.el9_7.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-debuginfo-common-x86_64-0:5.14.0-611.5.1.el9_7.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-devel-0:5.14.0-611.5.1.el9_7.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-devel-0:5.14.0-611.5.1.el9_7.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-devel-0:5.14.0-611.5.1.el9_7.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); kernel-devel-0:5.14.0-611.5.1.el9_7.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); and 273 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.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 16 Jul 2024 · Last source change 5 Aug 2026, 08:52 UTC · CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

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-2022-53709
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
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-2022-53709↗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-2022-48830 · cve.blacktree.nl