Linux Kernel up to 6.5.4 media az6007_i2c_xfer null pointer dereference

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.5$0-$5k0.00

Summaryinfo

A vulnerability classified as critical has been found in Linux Kernel up to 6.5.4. This affects the function az6007_i2c_xfer of the component media. The manipulation leads to null pointer dereference. This vulnerability is traded as CVE-2023-53220. There is no exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 6.5.4. This issue affects the function az6007_i2c_xfer of the component media. The manipulation with an unknown input leads to a null pointer dereference vulnerability. Using CWE to declare the problem leads to CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. Impacted is availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: media: az6007: Fix null-ptr-deref in az6007_i2c_xfer() In az6007_i2c_xfer, msg is controlled by user. When msg[i].buf is null and msg[i].len is zero, former checks on msg[i].buf would be passed. Malicious data finally reach az6007_i2c_xfer. If accessing msg[i].buf[0] without sanity check, null ptr deref would happen. We add check on msg[i].len to prevent crash. Similar commit: commit 0ed554fd769a ("media: dvb-usb: az6027: fix null-ptr-deref in az6027_i2c_xfer()")

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2023-53220 since 09/15/2025. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 270848 (SUSE SLES15 Security Update : kernel (SUSE-SU-2025:03626-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.14.326, 4.19.295, 5.4.257, 5.10.197, 5.15.133, 6.1.55 or 6.5.5 eliminates this vulnerability. Applying the patch c6763fefa267f6e62595a6ac1f57815d99fc90b7/adcb73f8ce9aec48b1f85223f401c1574015d8d2/991c77fe18c6f374bbf83376f8c42550aa565662/a9def3e9718a4dc756f48db147d42ec41a966240/5b1ea100ad3695025969dc4693f307877fb688d6/6ab7ea4e17d6a605d05308adf8f3408924770cba/a1110f19d4940e4185251d072cbb0ff51486a1e7/1047f9343011f2cedc73c64829686206a7e9fc3f is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (270848) and CERT Bund (WID-SEC-2025-2053). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • IBM QRadar SIEM
  • SUSE openSUSE
  • Open Source Linux Kernel
  • RESF Rocky Linux
  • Dell Secure Connect Gateway
  • F5 F5OS

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.6
VulDB Meta Temp Score: 5.5

VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Null pointer dereference
CWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 270848
Nessus Name: SUSE SLES15 Security Update : kernel (SUSE-SU-2025:03626-1)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 4.14.326/4.19.295/5.4.257/5.10.197/5.15.133/6.1.55/6.5.5
Patch: c6763fefa267f6e62595a6ac1f57815d99fc90b7/adcb73f8ce9aec48b1f85223f401c1574015d8d2/991c77fe18c6f374bbf83376f8c42550aa565662/a9def3e9718a4dc756f48db147d42ec41a966240/5b1ea100ad3695025969dc4693f307877fb688d6/6ab7ea4e17d6a605d05308adf8f3408924770cba/a1110f19d4940e4185251d072cbb0ff51486a1e7/1047f9343011f2cedc73c64829686206a7e9fc3f

Timelineinfo

09/15/2025 Advisory disclosed
09/15/2025 +0 days CVE reserved
09/15/2025 +0 days VulDB entry created
01/10/2026 +117 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2023-53220 (🔒)
GCVE (CVE): GCVE-0-2023-53220
GCVE (VulDB): GCVE-100-324029
CERT Bund: WID-SEC-2025-2053 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 09/15/2025 17:04
Updated: 01/10/2026 22:22
Changes: 09/15/2025 17:04 (59), 10/21/2025 21:08 (2), 12/03/2025 17:20 (10), 12/29/2025 03:14 (7), 01/10/2026 22:22 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!