🛡️ USN-6349-1 — linux-azure

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

Description

linux-azure vulnerabilities

Ruihan Li discovered that the bluetooth subsystem in the Linux kernel did

not properly perform permissions checks when handling HCI sockets. A

physically proximate attacker could use this to cause a denial of service

(bluetooth communication). (CVE-2023-2002)

Zi Fan Tan discovered that the binder IPC implementation in the Linux

kernel contained 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-21255)

Juan Jose Lopez Jaimez, Meador Inge, Simon Scannell, and Nenad Stojanovski

discovered that the BPF verifier in the Linux kernel did not properly mark

registers for precision tracking in certain situations, leading to an out-

of-bounds access vulnerability. A local attacker could use this to cause a

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

(CVE-2023-2163)

Zheng Zhang discovered that the device-mapper implementation in the Linux

kernel did not properly handle locking during table_clear() operations. A

local attacker could use this to cause a denial of service (kernel

deadlock). (CVE-2023-2269)

It was discovered that the DVB Core driver in the Linux kernel did not

properly handle locking events in certain situations. A local attacker

could use this to cause a denial of service (kernel deadlock).

(CVE-2023-31084)

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 video4linux driver for Philips based TV cards in

the Linux kernel contained a race condition during device removal, leading

to a use-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-35823)

It was discovered that the SDMC DM1105 PCI device driver in the Linux

kernel contained a race condition during device removal, leading to a use-

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-35824)

It was discovered that the Renesas USB controller driver in the Linux

kernel contained a race condition during device removal, leading to a use-

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

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

(CVE-2023-35828)

Affected software

USN-6349-1 is recorded against 1 package.

  • linux-azure (fixed in 5.4.0-1115.122)

Timeline and source

Published on 6 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)

Details

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

Affected Packages

Software From version Fixed in
linux-azure 5.4.0-1115.122

Similar Threats

Free Vulnerability Check

Is your site affected by USN-6349-1?

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