CVE-2023-53519 media: v4l2-mem2mem: add lock to protect parameter num_rdy

Medium 5.5 Published Updated

A race condition in the Linux kernel's v4l2-mem2mem driver can lead to data races and potential system instability or crashes.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2023-53519?

CVE-2023-53519 is a medium-severity vulnerability in Linux kernel, published on 1 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

In the Linux kernel, the following vulnerability has been resolved:

media: v4l2-mem2mem: add lock to protect parameter num_rdy

Getting below error when using KCSAN to check the driver. Adding lock to protect parameter num_rdy when getting the value with function: v4l2_m2m_num_src_bufs_ready/v4l2_m2m_num_dst_bufs_ready.

kworker/u16:3: [name:report&]BUG: KCSAN: data-race in v4l2_m2m_buf_queue kworker/u16:3: [name:report&]

kworker/u16:3: [name:report&]read-write to 0xffffff8105f35b94 of 1 bytes by task 20865 on cpu 7: kworker/u16:3:  v4l2_m2m_buf_queue+0xd8/0x10c

Weakness: CWE-667

Which versions are affected by CVE-2023-53519?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2023-53519?

Apply the vendor's patch.

Is CVE-2023-53519 being exploited?

There is no known exploitation of CVE-2023-53519 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as BELL-CVE-2023-53519, DEBIAN-CVE-2023-53519, GHSA-g4hw-wv9w-w499, UBUNTU-CVE-2023-53519.

Is CVE-2023-53519 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free