Linux vulnerability

In the Linux kernel, the following vulnerability has been resolved: media: dvbdev: prevent the risk of out of memory access The dvbdev contains a static variable used to store dvb minors. The behavior of it depends if CONFIG_DVB_DYNAMIC_MINORS is set or not. When not set, dvb_register_device() won't check for boundaries, as it will rely that a previous call to dvb_register_adapter() would already be enforcing it. On a similar way, dvb_device_open() uses the assumption that the register functions already did the needed checks. This can be fragile if some device ends using different calls. This also generate warnings on static check analysers like Coverity. So, add explicit guards to prevent potential risk of OOM issues.

Published 19 Nov 2024Updated 18 Sep 202610 sources
CVSS 7.8

What happened

In the Linux kernel, the following vulnerability has been resolved: media: dvbdev: prevent the risk of out of memory access The dvbdev contains a static variable used to store dvb minors. The behavior of it depends if CONFIG_DVB_DYNAMIC_MINORS is set or not. When not set, dvb_register_device() won't check for boundaries, as it will rely that a previous call to dvb_register_adapter() would already be enforcing it. On a similar way, dvb_device_open() uses the assumption that the register functions already did the needed checks. This can be fragile if some device ends using different calls. This also generate warnings on static check analysers like Coverity. So, add explicit guards to prevent potential risk of OOM issues.

Affected versions

Linux: 5dd3f3071070f5a306bdf8d474c80062f5691cba through before fedfde9deb83ac8d2f3d5f36f111023df34b1684 (git); 5dd3f3071070f5a306bdf8d474c80062f5691cba through before 3b88675e18b6517043a6f734eaa8ea6eb3bfa140 (git); 5dd3f3071070f5a306bdf8d474c80062f5691cba through before a4a17210c03ade1c8d9a9f193a105654b7a05c11 (git); 5dd3f3071070f5a306bdf8d474c80062f5691cba through before 5f76f7df14861e3a560898fa41979ec92424b58f (git); 5dd3f3071070f5a306bdf8d474c80062f5691cba through before b751a96025275c17f04083cbfe856822f1658946 (git); 5dd3f3071070f5a306bdf8d474c80062f5691cba through before 1e461672616b726f29261ee81bb991528818537c (git); 5dd3f3071070f5a306bdf8d474c80062f5691cba through before 9c17085fabbde2041c893d29599800f2d4992b23 (git); 5dd3f3071070f5a306bdf8d474c80062f5691cba through before 972e63e895abbe8aa1ccbdbb4e6362abda7cd457 (git); 2.6.29 Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

  • Apply vendor-provided updates or mitigations.
  • Review affected product exposure and access logs.

Public PoC references

No public PoC reference has passed the current publication threshold.