Bug 2367576 (CVE-2025-37971) - CVE-2025-37971 kernel: staging: bcm2835-camera: Initialise dev in v4l2_dev
Summary: CVE-2025-37971 kernel: staging: bcm2835-camera: Initialise dev in v4l2_dev
Keywords:
Status: NEW
Alias: CVE-2025-37971
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-05-20 17:01 UTC by OSIDB Bzimport
Modified: 2026-06-29 18:26 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-05-20 17:01:40 UTC
In the Linux kernel, the following vulnerability has been resolved:

staging: bcm2835-camera: Initialise dev in v4l2_dev

Commit 42a2f6664e18 ("staging: vc04_services: Move global g_state to
vchiq_state") changed mmal_init to pass dev->v4l2_dev.dev to
vchiq_mmal_init, however nothing iniitialised dev->v4l2_dev, so we got
a NULL pointer dereference.

Set dev->v4l2_dev.dev during bcm2835_mmal_probe. The device pointer
could be passed into v4l2_device_register to set it, however that also
has other effects that would need additional changes.

Comment 1 Jon Moroney 2025-05-21 01:51:02 UTC Comment hidden (spam)

Note You need to log in before you can comment on or make changes to this bug.