🛡️ USN-6337-1 — linux-azure-5.4

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

linux-azure-5.4 vulnerabilities

It was discovered that the netlink implementation in the Linux kernel did

not properly validate policies when parsing attributes in some situations.

An attacker could use this to cause a denial of service (infinite

recursion). (CVE-2020-36691)

Billy Jheng Bing Jhong discovered that the CIFS network file system

implementation in the Linux kernel did not properly validate arguments to

ioctl() in some situations. A local attacker could possibly use this to

cause a denial of service (system crash). (CVE-2022-0168)

It was discovered that the ext4 file system implementation in the Linux

kernel contained a use-after-free vulnerability. An attacker could use this

to construct a malicious ext4 file system image that, when mounted, could

cause a denial of service (system crash). (CVE-2022-1184)

It was discovered that some AMD x86-64 processors with SMT enabled could

speculatively execute instructions using a return address from a sibling

thread. A local attacker could possibly use this to expose sensitive

information. (CVE-2022-27672)

William Zhao discovered that the Traffic Control (TC) subsystem in the

Linux kernel did not properly handle network packet retransmission in

certain situations. A local attacker could use this to cause a denial of

service (kernel deadlock). (CVE-2022-4269)

It was discovered that a race condition existed in the qdisc implementation

in the Linux kernel, leading to a use-after-free vulnerability. A local

attacker could use this to cause a denial of service (system crash) or

possibly execute arbitrary code. (CVE-2023-0590)

It was discovered that a race condition existed in the btrfs file system

implementation in the Linux kernel, leading to a use-after-free

vulnerability. A local attacker could use this to cause a denial of service

(system crash) or possibly expose sensitive information. (CVE-2023-1611)

It was discovered that the APM X-Gene SoC hardware monitoring driver in the

Linux kernel contained a race condition, leading to a use-after-free

vulnerability. A local attacker could use this to cause a denial of service

(system crash) or expose sensitive information (kernel memory).

(CVE-2023-1855)

It was discovered that the ST NCI NFC driver did not properly handle device

removal events. A physically proximate attacker could use this to cause a

denial of service (system crash). (CVE-2023-1990)

It was discovered that the XFS file system implementation in the Linux

kernel did not properly perform metadata validation when mounting certain

images. An attacker could use this to specially craft a file system image

that, when mounted, could cause a denial of service (system crash).

(CVE-2023-2124)

It was discovered that the SLIMpro I2C device driver in the Linux kernel

did not properly validate user-supplied data in some situations, leading to

an out-of-bounds write vulnerability. A privileged attacker could use this

to cause a denial of service (system crash) or possibly execute arbitrary

code. (CVE-2023-2194)

It was discovered that a race condition existed in the TLS subsystem in the

Linux kernel, leading to a use-after-free or a null pointer dereference

vulnerability. A local attacker could use this to cause a denial of service

(system crash) or possibly execute arbitrary code. (CVE-2023-28466)

It was discovered that the DA9150 charger driver in the Linux kernel did

not properly handle device removal, leading to a user-after free

vulnerability. A physically proximate attacker could use this to cause a

denial of service (system crash) or possibly execute arbitrary code.

(CVE-2023-30772)

It was discovered that the btrfs file system implementation in the Linux

kernel did not properly handle error conditions in some situations, leading

to a use-after-free vulnerability. A local attacker could possibly use this

to cause a denial of service (system crash). (CVE-2023-3111)

It was discovered that the Ricoh R5C592 MemoryStick card reader driver in

the Linux kernel contained a race condition during module unload, leading

to a use-after-free vulnerability. A local attacker could use this to cause

a denial of service (system crash) or possibly execute arbitrary code.

(CVE-2023-3141)

It was discovered that the Qualcomm EMAC ethernet driver in the Linux

kernel did not properly handle device removal, leading to a user-after free

vulnerability. A physically proximate attacker could use this to cause a

denial of service (system crash) or possibly execute arbitrary code.

(CVE-2023-33203)

Affected software

USN-6337-1 is recorded against 1 package.

  • linux-azure-5.4 (fixed in 5.4.0-1113.119~18.04.1)

Timeline and source

Published on 4 September 2023 and last revised on 3 June 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

ubuntu.com (Advisory)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector N/A
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2023-09-04
Updated 2026-08-12
Modified 2026-06-03
Fix URL N/A

Affected Packages

Software From version Fixed in
linux-azure-5.4 5.4.0-1113.119~18.04.1

References

Similar Threats

Free Vulnerability Check

Is your site affected by USN-6337-1?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against USN-6337-1 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.