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

unspecified — Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

unspecified · unspecified

7.0HighCVSS 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 10 Sept 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

2 current
SSA-202008 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-202008: Multiple Vulnerabilities in Ruggedcom Rox Before V2.17.0
11 known affected

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

  • RUGGEDCOM ROX MX5000
  • RUGGEDCOM ROX MX5000RE
  • RUGGEDCOM ROX RX1400
  • RUGGEDCOM ROX RX1500
  • RUGGEDCOM ROX RX1501
  • RUGGEDCOM ROX RX1510
  • RUGGEDCOM ROX RX1511
  • RUGGEDCOM ROX RX1512
  • RUGGEDCOM ROX RX1524
  • RUGGEDCOM ROX RX1536
  • RUGGEDCOM ROX RX5000
Summary
Linux PV device frontends vulnerable to attacks by backends [This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Several Linux PV device frontends are using the grant table interfaces for removing access rights of the backends in ways being subject to race conditions, resulting in potential data leaks, data corruption by malicious backends, and denial of service triggered by malicious backends: blkfront, netfront, scsifront and the gntalloc driver are testing whether a grant reference is still in use. If this is not the case, they assume that a following removal of the granted access will always succeed, which is not true in case the backend has mapped the granted page between those two operations. As a result the backend can keep access to the memory page of the guest no matter how the page will be used after the frontend I/O has finished. The xenbus driver has a similar problem, as it doesn't check the success of removing the granted access of a shared ring buffer. blkfront: CVE-2022-23036 netfront: CVE-2022-23037 scsifront: CVE-2022-23038 gntalloc: CVE-2022-23039 xenbus: CVE-2022-23040 blkfront, netfront, scsifront, usbfront, dmabuf, xenbus, 9p, kbdfront, and pvcalls are using a functionality to delay freeing a grant reference until it is no longer in use, but the freeing of the related data page is not synchronized with dropping the granted access. As a result the backend can keep access to the memory page even after it has been freed and then re-used for a different purpose. CVE-2022-23041 netfront will fail a BUG_ON() assertion if it fails to revoke access in the rx path. This will result in a Denial of Service (DoS) situation of the guest which can be triggered by the backend.
Remediation
Update to V2.17.0 or later version
SSA-419740 · CSAF 2.0 · revision 1 · finalSiemens ProductCERTSSA-419740: Multiple Third-Party Component Vulnerabilities in RUGGEDCOM and SCALANCE Products before V7.2
20 known affected

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

  • RUGGEDCOM RM1224 LTE(4G) EU (6GK6108-4AM00-2BA2)
  • RUGGEDCOM RM1224 LTE(4G) NAM (6GK6108-4AM00-2DA2)
  • SCALANCE M804PB (6GK5804-0AP00-2AA2)
  • SCALANCE M812-1 ADSL-Router (Annex A) (6GK5812-1AA00-2AA2)
  • SCALANCE M812-1 ADSL-Router (Annex B) (6GK5812-1BA00-2AA2)
  • SCALANCE M816-1 ADSL-Router (Annex A) (6GK5816-1AA00-2AA2)
  • SCALANCE M816-1 ADSL-Router (Annex B) (6GK5816-1BA00-2AA2)
  • SCALANCE M826-2 SHDSL-Router (6GK5826-2AB00-2AB2)
  • SCALANCE M874-2 (6GK5874-2AA00-2AA2)
  • SCALANCE M874-3 (6GK5874-3AA00-2AA2)
  • SCALANCE M876-3 (EVDO) (6GK5876-3AA02-2BA2)
  • SCALANCE M876-3 (ROK) (6GK5876-3AA02-2EA2)
Summary
Linux PV device frontends vulnerable to attacks by backends [This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Several Linux PV device frontends are using the grant table interfaces for removing access rights of the backends in ways being subject to race conditions, resulting in potential data leaks, data corruption by malicious backends, and denial of service triggered by malicious backends: blkfront, netfront, scsifront and the gntalloc driver are testing whether a grant reference is still in use. If this is not the case, they assume that a following removal of the granted access will always succeed, which is not true in case the backend has mapped the granted page between those two operations. As a result the backend can keep access to the memory page of the guest no matter how the page will be used after the frontend I/O has finished. The xenbus driver has a similar problem, as it doesn't check the success of removing the granted access of a shared ring buffer. blkfront: CVE-2022-23036 netfront: CVE-2022-23037 scsifront: CVE-2022-23038 gntalloc: CVE-2022-23039 xenbus: CVE-2022-23040 blkfront, netfront, scsifront, usbfront, dmabuf, xenbus, 9p, kbdfront, and pvcalls are using a functionality to delay freeing a grant reference until it is no longer in use, but the freeing of the related data page is not synchronized with dropping the granted access. As a result the backend can keep access to the memory page even after it has been freed and then re-used for a different purpose. CVE-2022-23041 netfront will fail a BUG_ON() assertion if it fails to revoke access in the rx path. This will result in a Denial of Service (DoS) situation of the guest which can be triggered by the backend.
Remediation
Update to V7.2 or later version
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-28151

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

Linux PV device frontends vulnerable to attacks by backends T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Several Linux PV device frontends are using the grant table interfaces for removing access rights of the backends in ways being subject to race conditions, resulting in potential data leaks, data corruption by malicious backends, and denial of service triggered by malicious backends: blkfront, netfront, scsifront and the gntalloc driver are testing whether a grant reference is still in use. If this is not the case, they assume that a following removal of the granted access will always succeed, which is not true in case the backend has mapped the granted page between those two operations. As a result the backend can keep access to the memory page of the guest no matter how the page will be used after the frontend I/O has finished. The xenbus driver has a similar problem, as it doesn't check the success of removing the granted access of a shared ring buffer. blkfront: CVE-2022-23036 netfront: CVE-2022-23037 scsifront: CVE-2022-23038 gntalloc: CVE-2022-23039 xenbus: CVE-2022-23040 blkfront, netfront, scsifront, usbfront, dmabuf, xenbus, 9p, kbdfront, and pvcalls are using a functionality to delay freeing a grant reference until it is no longer in use, but the freeing of the related data page is not synchronized with dropping the granted access. As a result the backend can keep access to the memory page even after it has been freed and then re-used for a different purpose. CVE-2022-23041 netfront will fail a BUG_ON() assertion if it fails to revoke access in the rx path. This will result in a Denial of Service (DoS) situation of the guest which can be triggered by the backend. CVE-2022-23042

What

Linux PV device frontends vulnerable to attacks by backends T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Several Linux PV device frontends are using the grant table interfaces for removing access rights of the backends in ways being subject to race conditions, resulting in potential data leaks, data corruption by malicious backends, and denial of service triggered by malicious backends: blkfront, netfront, scsifront and the gntalloc driver are testing whether a grant reference is still in use. If this is not the case, they assume that a following removal of the granted access will always succeed, which is not true in case the backend has mapped the granted page between those two operations. As a result the backend can keep access to the memory page of the guest no matter how the page will be used after the frontend I/O has finished. The xenbus driver has a similar problem, as it doesn't check the success of removing the granted access of a shared ring buffer. blkfront: CVE-2022-23036 netfront: CVE-2022-23037 scsifront: CVE-2022-23038 gntalloc: CVE-2022-23039 xenbus: CVE-2022-23040 blkfront, netfront, scsifront, usbfront, dmabuf, xenbus, 9p, kbdfront, and pvcalls are using a functionality to delay freeing a grant reference until it is no longer in use, but the freeing of the related data page is not synchronized with dropping the granted access. As a result the backend can keep access to the memory page even after it has been freed and then re-used for a different purpose. CVE-2022-23041 netfront will fail a BUG_ON() assertion if it fails to revoke access in the rx path. This will result in a Denial of Service (DoS) situation of the guest which can be triggered by the backend. CVE-2022-23042

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 local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

What

Linux PV device frontends vulnerable to attacks by backends T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Several Linux PV device frontends are using the grant table interfaces for removing access rights of the backends in ways being subject to race conditions, resulting in potential data leaks, data corruption by malicious backends, and denial of service triggered by malicious backends: blkfront, netfront, scsifront and the gntalloc driver are testing whether a grant reference is still in use. If this is not the case, they assume that a following removal of the granted access will always succeed, which is not true in case the backend has mapped the granted page between those two operations. As a result the backend can keep access to the memory page of the guest no matter how the page will be used after the frontend I/O has finished. The xenbus driver has a similar problem, as it doesn't check the success of removing the granted access of a shared ring buffer. blkfront: CVE-2022-23036 netfront: CVE-2022-23037 scsifront: CVE-2022-23038 gntalloc: CVE-2022-23039 xenbus: CVE-2022-23040 blkfront, netfront, scsifront, usbfront, dmabuf, xenbus, 9p, kbdfront, and pvcalls are using a functionality to delay freeing a grant reference until it is no longer in use, but the freeing of the related data page is not synchronized with dropping the granted access. As a result the backend can keep access to the memory page even after it has been freed and then re-used for a different purpose. CVE-2022-23041 netfront will fail a BUG_ON() assertion if it fails to revoke access in the rx path. This will result in a Denial of Service (DoS) situation of the guest which can be triggered by the backend. CVE-2022-23042

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 local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

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 → Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') → disrupt the affected service
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
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:L/AC:H/PR:L/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.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.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.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
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
Denial of serviceCWE-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-2022-0154Xen: Mehrere Schwachstellen ermöglichen Umgehen von Sicherheitsvorkehrungen

Ein lokaler Angreifer kann mehrere Schwachstellen in Xen ausnutzen, um Sicherheitsvorkehrungen zu umgehen oder einen Denial of Service Zustand herbeizuführen.

Official advisory
CERT-FR · French · CERTFR-2023-AVI-0220Multiples vulnérabilités dans les produits Siemens

VERecord?id=CVE-2022-1729 Référence CVE CVE-2022-1734 https://www.cve.org/CVERecord?id=CVE-2022-1734 Référence CVE CVE-2022-1974 https://www.cve.org/CVERecord?id=CVE-2022-1974 Référence CVE CVE-2022-1975 https://www.cve.org/CVERecord?id=CVE-2022-1975 Référence CVE CVE-2022-20158 https://www.cve.org/CVERecord?id=CVE-2022-20158 Référence CVE CVE-2022-23036 https://www.cve.org/CVERecord?id=CVE-2022-23036 Référence CVE CVE-2022-23037 https://www.cve.org/CVERecord?id=CVE-2022-23037 Référence CVE CVE-2022-23038 https://www.cve.org/CVERecord?id=CVE-2022-23038 Référence CVE CVE-2022-23039 https://www.cve.org/CVERecord?id=CVE-2022-23039 Référence CVE CVE-2022-23040 https://www.cve.org/CVERecord?id=CVE-2022-23040 Référence CVE CVE-2022-23041 https://www.cve.org/CVERecord?id=CVE-2022-23041 Référence CVE CVE-2022-23042 https://www.cve.org/CVERecord?id=CVE-2022-23042 Référence CVE CVE-2022-23308 https://www.cve.org/CVERecord?id=CVE-2022-23308 Référence CVE CVE-2022-23395 https://www.cve.org/CVERecord?id=CVE-2022-23395 Référence CVE CVE-2022-2380 https://www.cve.org/CVERecord?id=CVE-2022-2380 Référence CVE CVE-2022-24281 https://www.cve.org/CVERecord?id=CVE-2022-24281 Référence CVE CVE-2022-24282 https://www.cve.org/CVERecord?id=CVE-2022-24282 Référence CVE CVE-2022-25311 https://www.cve.org/CVERecord?id=CV

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

cord?id=CVE-2022-1975 Référence CVE CVE-2022-21123 https://www.cve.org/CVERecord?id=CVE-2022-21123 Référence CVE CVE-2022-21125 https://www.cve.org/CVERecord?id=CVE-2022-21125 Référence CVE CVE-2022-21166 https://www.cve.org/CVERecord?id=CVE-2022-21166 Référence CVE CVE-2022-2153 https://www.cve.org/CVERecord?id=CVE-2022-2153 Référence CVE CVE-2022-23036 https://www.cve.org/CVERecord?id=CVE-2022-23036 Référence CVE CVE-2022-23037 https://www.cve.org/CVERecord?id=CVE-2022-23037 Référence CVE CVE-2022-23038 https://www.cve.org/CVERecord?id=CVE-2022-23038 Référence CVE CVE-2022-23039 https://www.cve.org/CVERecord?id=CVE-2022-23039 Référence CVE CVE-2022-23040 https://www.cve.org/CVERecord?id=CVE-2022-23040 Référence CVE CVE-2022-23041 https://www.cve.org/CVERecord?id=CVE-2022-23041 Référence CVE CVE-2022-23042 https://www.cve.org/CVERecord?id=CVE-2022-23042 Référence CVE CVE-2022-23960 https://www.cve.org/CVERecord?id=CVE-2022-23960 Référence CVE CVE-2022-24958 https://www.cve.org/CVERecord?id=CVE-2022-24958 Référence CVE CVE-2022-26490 https://www.cve.org/CVERecord?id=CVE-2022-26490 Référence CVE CVE-2022-26966 https://www.cve.org/CVERecord?id=CVE-2022-26966 Référence CVE CVE-2022-27223 https://www.cve.org/CVERecord?id=CVE-2022-27223 Référence CVE CVE-2022-28356 https://www.cve.org/CVERecord?id=

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

VERecord?id=CVE-2022-1734 Référence CVE CVE-2022-1836 https://www.cve.org/CVERecord?id=CVE-2022-1836 Référence CVE CVE-2022-1966 https://www.cve.org/CVERecord?id=CVE-2022-1966 Référence CVE CVE-2022-1972 https://www.cve.org/CVERecord?id=CVE-2022-1972 Référence CVE CVE-2022-21499 https://www.cve.org/CVERecord?id=CVE-2022-21499 Référence CVE CVE-2022-23036 https://www.cve.org/CVERecord?id=CVE-2022-23036 Référence CVE CVE-2022-23037 https://www.cve.org/CVERecord?id=CVE-2022-23037 Référence CVE CVE-2022-23038 https://www.cve.org/CVERecord?id=CVE-2022-23038 Référence CVE CVE-2022-23039 https://www.cve.org/CVERecord?id=CVE-2022-23039 Référence CVE CVE-2022-23040 https://www.cve.org/CVERecord?id=CVE-2022-23040 Référence CVE CVE-2022-23041 https://www.cve.org/CVERecord?id=CVE-2022-23041 Référence CVE CVE-2022-23042 https://www.cve.org/CVERecord?id=CVE-2022-23042 Référence CVE CVE-2022-24958 https://www.cve.org/CVERecord?id=CVE-2022-24958 Référence CVE CVE-2022-26966 https://www.cve.org/CVERecord?id=CVE-2022-26966 Référence CVE CVE-2022-28356 https://www.cve.org/CVERecord?id=CVE-2022-28356 Référence CVE CVE-2022-28388 https://www.cve.org/CVERecord?id=CVE-2022-28388 Référence CVE CVE-2022-28389 https://www.cve.org/CVERecord?id=CVE-2022-28389 Référence CVE CVE-2022-28390 https://www.cve.org/CVERecord?id=

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

VERecord?id=CVE-2021-4157 Référence CVE CVE-2022-1016 https://www.cve.org/CVERecord?id=CVE-2022-1016 Référence CVE CVE-2022-1158 https://www.cve.org/CVERecord?id=CVE-2022-1158 Référence CVE CVE-2022-1516 https://www.cve.org/CVERecord?id=CVE-2022-1516 Référence CVE CVE-2022-20008 https://www.cve.org/CVERecord?id=CVE-2022-20008 Référence CVE CVE-2022-23036 https://www.cve.org/CVERecord?id=CVE-2022-23036 Référence CVE CVE-2022-23037 https://www.cve.org/CVERecord?id=CVE-2022-23037 Référence CVE CVE-2022-23038 https://www.cve.org/CVERecord?id=CVE-2022-23038 Référence CVE CVE-2022-23039 https://www.cve.org/CVERecord?id=CVE-2022-23039 Référence CVE CVE-2022-23040 https://www.cve.org/CVERecord?id=CVE-2022-23040 Référence CVE CVE-2022-23042 https://www.cve.org/CVERecord?id=CVE-2022-23042 Référence CVE CVE-2022-24958 https://www.cve.org/CVERecord?id=CVE-2022-24958 Référence CVE CVE-2022-25258 https://www.cve.org/CVERecord?id=CVE-2022-25258 Référence CVE CVE-2022-25375 https://www.cve.org/CVERecord?id=CVE-2022-25375 Référence CVE CVE-2022-26490 https://www.cve.org/CVERecord?id=CVE-2022-26490 Référence CVE CVE-2022-26966 https://www.cve.org/CVERecord?id=CVE-2022-26966 Référence CVE CVE-2022-27223 https://www.cve.org/CVERecord?id=CVE-2022-27223 Référence CVE CVE-2022-28388 https://www.cve.org/CVERecord?id=

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

/CVERecord?id=CVE-2022-1055 Référence CVE CVE-2022-1195 https://www.cve.org/CVERecord?id=CVE-2022-1195 Référence CVE CVE-2022-1198 https://www.cve.org/CVERecord?id=CVE-2022-1198 Référence CVE CVE-2022-1199 https://www.cve.org/CVERecord?id=CVE-2022-1199 Référence CVE CVE-2022-1205 https://www.cve.org/CVERecord?id=CVE-2022-1205 Référence CVE CVE-2022-23036 https://www.cve.org/CVERecord?id=CVE-2022-23036 Référence CVE CVE-2022-23037 https://www.cve.org/CVERecord?id=CVE-2022-23037 Référence CVE CVE-2022-23038 https://www.cve.org/CVERecord?id=CVE-2022-23038 Référence CVE CVE-2022-23039 https://www.cve.org/CVERecord?id=CVE-2022-23039 Référence CVE CVE-2022-23040 https://www.cve.org/CVERecord?id=CVE-2022-23040 Référence CVE CVE-2022-23041 https://www.cve.org/CVERecord?id=CVE-2022-23041 Référence CVE CVE-2022-23042 https://www.cve.org/CVERecord?id=CVE-2022-23042 Référence CVE CVE-2022-26490 https://www.cve.org/CVERecord?id=CVE-2022-26490 Référence CVE CVE-2022-26966 https://www.cve.org/CVERecord?id=CVE-2022-26966 Référence CVE CVE-2022-27666 https://www.cve.org/CVERecord?id=CVE-2022-27666 Référence CVE CVE-2022-28356 https://www.cve.org/CVERecord?id=CVE-2022-28356 Référence CVE CVE-2022-28388 https://www.cve.org/CVERecord?id=CVE-2022-28388 Référence CVE CVE-2022-28389 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2022-AVI-374Multiples 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 un problème de sécurité non spécifié par l'éditeur, un déni de service et une atteinte à la confidentialité des données.

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

/CVERecord?id=CVE-2022-0854 Référence CVE CVE-2022-0886 https://www.cve.org/CVERecord?id=CVE-2022-0886 Référence CVE CVE-2022-1016 https://www.cve.org/CVERecord?id=CVE-2022-1016 Référence CVE CVE-2022-1048 https://www.cve.org/CVERecord?id=CVE-2022-1048 Référence CVE CVE-2022-1055 https://www.cve.org/CVERecord?id=CVE-2022-1055 Référence CVE CVE-2022-23036 https://www.cve.org/CVERecord?id=CVE-2022-23036 Référence CVE CVE-2022-23037 https://www.cve.org/CVERecord?id=CVE-2022-23037 Référence CVE CVE-2022-23038 https://www.cve.org/CVERecord?id=CVE-2022-23038 Référence CVE CVE-2022-23039 https://www.cve.org/CVERecord?id=CVE-2022-23039 Référence CVE CVE-2022-23040 https://www.cve.org/CVERecord?id=CVE-2022-23040 Référence CVE CVE-2022-23041 https://www.cve.org/CVERecord?id=CVE-2022-23041 Référence CVE CVE-2022-23042 https://www.cve.org/CVERecord?id=CVE-2022-23042 Référence CVE CVE-2022-24448 https://www.cve.org/CVERecord?id=CVE-2022-24448 Référence CVE CVE-2022-24958 https://www.cve.org/CVERecord?id=CVE-2022-24958 Référence CVE CVE-2022-24959 https://www.cve.org/CVERecord?id=CVE-2022-24959 Référence CVE CVE-2022-25258 https://www.cve.org/CVERecord?id=CVE-2022-25258 Référence CVE CVE-2022-25375 https://www.cve.org/CVERecord?id=CVE-2022-25375 Référence CVE CVE-2022-26490 https://www.cve.org/CVERecord?id=

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

VERecord?id=CVE-2022-0854 Référence CVE CVE-2022-1016 https://www.cve.org/CVERecord?id=CVE-2022-1016 Référence CVE CVE-2022-1048 https://www.cve.org/CVERecord?id=CVE-2022-1048 Référence CVE CVE-2022-1055 https://www.cve.org/CVERecord?id=CVE-2022-1055 Référence CVE CVE-2022-22942 https://www.cve.org/CVERecord?id=CVE-2022-22942 Référence CVE CVE-2022-23036 https://www.cve.org/CVERecord?id=CVE-2022-23036 Référence CVE CVE-2022-23037 https://www.cve.org/CVERecord?id=CVE-2022-23037 Référence CVE CVE-2022-23038 https://www.cve.org/CVERecord?id=CVE-2022-23038 Référence CVE CVE-2022-23039 https://www.cve.org/CVERecord?id=CVE-2022-23039 Référence CVE CVE-2022-23040 https://www.cve.org/CVERecord?id=CVE-2022-23040 Référence CVE CVE-2022-23041 https://www.cve.org/CVERecord?id=CVE-2022-23041 Référence CVE CVE-2022-23042 https://www.cve.org/CVERecord?id=CVE-2022-23042 Référence CVE CVE-2022-23960 https://www.cve.org/CVERecord?id=CVE-2022-23960 Référence CVE CVE-2022-26490 https://www.cve.org/CVERecord?id=CVE-2022-26490 Référence CVE CVE-2022-26966 https://www.cve.org/CVERecord?id=CVE-2022-26966 Référence CVE CVE-2022-27666 https://www.cve.org/CVERecord?id=CVE-2022-27666 Référence CVE CVE-2022-28388 https://www.cve.org/CVERecord?id=CVE-2022-28388 Référence CVE CVE-2022-28389 https://www.cve.org/CVERecord?id=

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

VERecord?id=CVE-2022-1195 Référence CVE CVE-2022-1198 https://www.cve.org/CVERecord?id=CVE-2022-1198 Référence CVE CVE-2022-1199 https://www.cve.org/CVERecord?id=CVE-2022-1199 Référence CVE CVE-2022-1205 https://www.cve.org/CVERecord?id=CVE-2022-1205 Référence CVE CVE-2022-22942 https://www.cve.org/CVERecord?id=CVE-2022-22942 Référence CVE CVE-2022-23036 https://www.cve.org/CVERecord?id=CVE-2022-23036 Référence CVE CVE-2022-23037 https://www.cve.org/CVERecord?id=CVE-2022-23037 Référence CVE CVE-2022-23038 https://www.cve.org/CVERecord?id=CVE-2022-23038 Référence CVE CVE-2022-23039 https://www.cve.org/CVERecord?id=CVE-2022-23039 Référence CVE CVE-2022-23040 https://www.cve.org/CVERecord?id=CVE-2022-23040 Référence CVE CVE-2022-23041 https://www.cve.org/CVERecord?id=CVE-2022-23041 Référence CVE CVE-2022-23042 https://www.cve.org/CVERecord?id=CVE-2022-23042 Référence CVE CVE-2022-27223 https://www.cve.org/CVERecord?id=CVE-2022-27223 Référence CVE CVE-2022-27666 https://www.cve.org/CVERecord?id=CVE-2022-27666 Référence CVE CVE-2022-28388 https://www.cve.org/CVERecord?id=CVE-2022-28388 Référence CVE CVE-2022-28389 https://www.cve.org/CVERecord?id=CVE-2022-28389 Référence CVE CVE-2022-28390 https://www.cve.org/CVERecord?id=CVE-2022-28390 Gestion détaillée du document le 14 avril 2022 Version initial

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

/CVERecord?id=CVE-2022-0487 Référence CVE CVE-2022-0492 https://www.cve.org/CVERecord?id=CVE-2022-0492 Référence CVE CVE-2022-0516 https://www.cve.org/CVERecord?id=CVE-2022-0516 Référence CVE CVE-2022-0617 https://www.cve.org/CVERecord?id=CVE-2022-0617 Référence CVE CVE-2022-0644 https://www.cve.org/CVERecord?id=CVE-2022-0644 Référence CVE CVE-2022-23036 https://www.cve.org/CVERecord?id=CVE-2022-23036 Référence CVE CVE-2022-23037 https://www.cve.org/CVERecord?id=CVE-2022-23037 Référence CVE CVE-2022-23038 https://www.cve.org/CVERecord?id=CVE-2022-23038 Référence CVE CVE-2022-23039 https://www.cve.org/CVERecord?id=CVE-2022-23039 Référence CVE CVE-2022-23040 https://www.cve.org/CVERecord?id=CVE-2022-23040 Référence CVE CVE-2022-23041 https://www.cve.org/CVERecord?id=CVE-2022-23041 Référence CVE CVE-2022-23042 https://www.cve.org/CVERecord?id=CVE-2022-23042 Référence CVE CVE-2022-24448 https://www.cve.org/CVERecord?id=CVE-2022-24448 Référence CVE CVE-2022-24958 https://www.cve.org/CVERecord?id=CVE-2022-24958 Référence CVE CVE-2022-24959 https://www.cve.org/CVERecord?id=CVE-2022-24959 Référence CVE CVE-2022-25258 https://www.cve.org/CVERecord?id=CVE-2022-25258 Référence CVE CVE-2022-25636 https://www.cve.org/CVERecord?id=CVE-2022-25636 Référence CVE CVE-2022-26490 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2022-AVI-236Multiples vulnérabilités dans Xen

De multiples vulnérabilités ont été découvertes dans Xen. Elles permettent à un attaquant de provoquer un déni de service, une atteinte à l'intégrité des données et une atteinte à la confidentialité des données.

Official advisory
NCSC-NL · Dutch · NCSC-2025-0382Kwetsbaarheden verholpen in Siemens producten

SUSE Linux Enterprise kernels across various versions have been updated to address multiple security vulnerabilities, including memory leaks, buffer overflows, and double free issues, alongside numerous non-security bug fixes.

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
RUGGEDCOM ROX MX5000; RUGGEDCOM ROX MX5000RE; RUGGEDCOM ROX RX1400; RUGGEDCOM ROX RX1500; RUGGEDCOM ROX RX1501; RUGGEDCOM ROX RX1510; RUGGEDCOM ROX RX1511; RUGGEDCOM ROX RX1512; RUGGEDCOM ROX RX1524; RUGGEDCOM ROX RX1536; RUGGEDCOM ROX RX5000
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
Update to V2.17.0 or later version
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 10 Mar 2022 · Last source change 3 Aug 2024, 03:28 UTC · CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVE recordCVE.org · 5.1
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-2022-28151
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
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
ENISA EUVD · EUVD-2022-28151↗Vendor CSAF · Siemens ProductCERT↗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-2022-23040 · cve.blacktree.nl