CVE-2026-31473: media: mc, v4l2: serialize REINIT and REQBUFS with req_queue_mutex

Published Apr 22, 2026
·
Updated

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

media: mc, v4l2: serialize REINIT and REQBUFS with reqqueuemutex

MEDIAREQUESTIOCREINIT can run concurrently with VIDIOCREQBUFS(0) queue teardown paths. This can race request object cleanup against vb2 queue cancellation and lead to use-after-free reports.

We already serialize request queueing against STREAMON/OFF with reqqueuemutex. Extend that serialization to REQBUFS, and also take the same mutex in mediarequestioctlreinit() so REINIT is in the same exclusion domain.

This keeps request cleanup and queue cancellation from running in parallel for request-capable devices.

Affected Software

19 affected componentsFixes available
Linux Linux kernel
Microsoft azl3 kernel 6.6.130.1-3
Microsoft azl3 kernel 6.6.130.1-3<6.6.134.1-2
6.6.134.1-2
Linux Linux kernel>=4.20.1<5.10.253
Linux Linux kernel>=5.11<5.15.203
Linux Linux kernel>=5.16<6.1.168
Linux Linux kernel>=6.2<6.6.131
Linux Linux kernel>=6.7<6.12.80
Linux Linux kernel>=6.13<6.18.21
Linux Linux kernel>=6.19<6.19.11
Linux Linux kernel=4.20
Linux Linux kernel=7.0-rc1
Linux Linux kernel=7.0-rc2
Linux Linux kernel=7.0-rc3
Linux Linux kernel=7.0-rc4
Linux Linux kernel=7.0-rc5
Linux Linux kernel=7.0-rc6
Linux Linux kernel=7.0-rc7
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.134.1-2
  2. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1
  3. Compensating control

    In media_request_ioctl_reinit(), take req_queue_mutex so MEDIA_REQUEST_IOC_REINIT and VIDIOC_REQBUFS(0) queue teardown execute in the same exclusion domain and cannot race.

Event History

Apr 22, 2026
CVE Published
via MITRE·01:54 PM
Data Sourced
via MITRE·01:54 PM
DescriptionSeverity
Data Sourced
via NVD·02:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Apr 23, 2026
Data Sourced
via Microsoft·08:09 AM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2026-31473?

CVE-2026-31473 has a high severity rating due to its potential impact on system stability and security.

2

How do I fix CVE-2026-31473?

To fix CVE-2026-31473, update your Linux kernel to a version that has addressed this vulnerability.

3

Which Linux kernel versions are affected by CVE-2026-31473?

CVE-2026-31473 affects Linux kernel versions from 4.20.1 up to 5.10.253 and versions across multiple ranges until 7.0-rc7.

4

What is the impact of CVE-2026-31473 on system performance?

CVE-2026-31473 could lead to performance degradation due to potential race conditions in media request handling.

5

Is CVE-2026-31473 exploitable remotely?

Yes, CVE-2026-31473 can potentially be exploited remotely if an attacker gains access to the media interface on the affected system.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203