🛡️ USN-6252-1 — linux

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

Description

linux, linux-aws, linux-aws-hwe, linux-azure, linux-azure-4.15, linux-dell300x, linux-gcp, linux-gcp-4.15, linux-hwe, linux-kvm, linux-oracle, linux-snapdragon vulnerabilities

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 the sound subsystem in the Linux kernel contained a

race condition in some situations. A local attacker could use this to cause

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

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 Xircom PCMCIA network device driver in the Linux

kernel did not properly handle device removal events. A physically

proximate attacker could use this to cause a denial of service (system

crash). (CVE-2023-1670)

It was discovered that a race condition existed in the Xen transport layer

implementation for the 9P file system protocol in the Linux kernel, leading

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

a denial of service (guest crash) or expose sensitive information (guest

kernel memory). (CVE-2023-1859)

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 IP-VLAN network driver for the Linux kernel did

not properly initialize memory in some situations, leading to an out-of-

bounds write vulnerability. An attacker could use this to cause a denial of

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

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 kernel->user space relay implementation in the

Linux kernel did not properly perform certain buffer calculations, leading

to an out-of-bounds read vulnerability. A local attacker could use this to

cause a denial of service (system crash) or expose sensitive information

(kernel memory). (CVE-2023-3268)

It was discovered that the netfilter subsystem in the Linux kernel did not

properly handle some error conditions, 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-3390)

Tanguy Dubroca discovered that the netfilter subsystem in the Linux kernel

did not properly handle certain pointer data type, 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-35001)

Affected software

USN-6252-1 is recorded against 12 packages.

  • linux (fixed in 4.15.0-214.225)
  • linux-aws (fixed in 4.15.0-1159.172)
  • linux-aws-hwe (fixed in 4.15.0-1159.172~16.04.1)
  • linux-azure (fixed in 4.15.0-1168.183~16.04.1)
  • linux-azure-4.15 (fixed in 4.15.0-1168.183)
  • linux-dell300x (fixed in 4.15.0-1068.73)
  • linux-gcp (fixed in 4.15.0-1153.170~16.04.1)
  • linux-gcp-4.15 (fixed in 4.15.0-1153.170)
  • linux-hwe (fixed in 4.15.0-214.225~16.04.1)
  • linux-kvm (fixed in 4.15.0-1143.148)
  • linux-oracle (fixed in 4.15.0-1122.133)
  • linux-snapdragon (fixed in 4.15.0-1153.163)

Timeline and source

Published on 26 July 2023 and last revised on 29 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)

Details

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

Affected Packages

Software From version Fixed in
linux 4.15.0-214.225
linux-aws 4.15.0-1159.172
linux-aws-hwe 4.15.0-1159.172~16.04.1
linux-azure 4.15.0-1168.183~16.04.1
linux-azure-4.15 4.15.0-1168.183
linux-dell300x 4.15.0-1068.73
linux-gcp 4.15.0-1153.170~16.04.1
linux-gcp-4.15 4.15.0-1153.170
linux-hwe 4.15.0-214.225~16.04.1
linux-kvm 4.15.0-1143.148
linux-oracle 4.15.0-1122.133
linux-snapdragon 4.15.0-1153.163

Similar Threats

Free Vulnerability Check

Is your site affected by USN-6252-1?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against USN-6252-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.