<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 19 Nov 2026 17:22:35 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-50175 — media: qcom: camss: Remove use_count guard in stop_streaming</title>
      <link>https://db.gcve.eu/vuln/cve-2024-50175</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: qcom: camss: Remove use_count guard in stop_streaming&lt;/p&gt;
&lt;p&gt;The use_count check was introduced so that multiple concurrent Raw Data
Interfaces RDIs could be driven by different virtual channels VCs on the
CSIPHY input driving the video pipeline.&lt;/p&gt;
&lt;p&gt;This is an invalid use of use_count though as use_count pertains to the
number of times a video entity has been opened by user-space not the number
of active streams.&lt;/p&gt;
&lt;p&gt;If use_count and stream-on count don&amp;#39;t agree then stop_streaming() will
break as is currently the case and has become apparent when using CAMSS
with libcamera&amp;#39;s released softisp 0.3.&lt;/p&gt;
&lt;p&gt;The use of use_count like this is a bit hacky and right now breaks regular
usage of CAMSS for a single stream case. Stopping qcam results in the splat
below, and then it cannot be started again and any attempts to do so fails
with -EBUSY.&lt;/p&gt;
&lt;p&gt;[ 1265.509831] WARNING: CPU: 5 PID: 919 at drivers/media/common/videobuf2/videobuf2-core.c:2183 __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common]
...
[ 1265.510630] Call trace:
[ 1265.510636]  __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common]
[ 1265.510648]  vb2_core_streamoff+0x24/0xcc [videobuf2_common]
[ 1265.510660]  vb2_ioctl_streamoff+0x5c/0xa8 [videobuf2_v4l2]
[ 1265.510673]  v4l_streamoff+0x24/0x30 [videodev]
[ 1265.510707]  __video_do_ioctl+0x190/0x3f4 [videodev]
[ 1265.510732]  video_usercopy+0x304/0x8c4 [videodev]
[ 1265.510757]  video_ioctl2+0x18/0x34 [videodev]
[ 1265.5…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: qcom: camss: Remove use_count guard in stop_streaming&lt;/p&gt;
&lt;p&gt;The use_count check was introduced so that multiple concurrent Raw Data
Interfaces RDIs could be driven by different virtual channels VCs on the
CSIPHY input driving the video pipeline.&lt;/p&gt;
&lt;p&gt;This is an invalid use of use_count though as use_count pertains to the
number of times a video entity has been opened by user-space not the number
of active streams.&lt;/p&gt;
&lt;p&gt;If use_count and stream-on count don&amp;#39;t agree then stop_streaming() will
break as is currently the case and has become apparent when using CAMSS
with libcamera&amp;#39;s released softisp 0.3.&lt;/p&gt;
&lt;p&gt;The use of use_count like this is a bit hacky and right now breaks regular
usage of CAMSS for a single stream case. Stopping qcam results in the splat
below, and then it cannot be started again and any attempts to do so fails
with -EBUSY.&lt;/p&gt;
&lt;p&gt;[ 1265.509831] WARNING: CPU: 5 PID: 919 at drivers/media/common/videobuf2/videobuf2-core.c:2183 __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common]
...
[ 1265.510630] Call trace:
[ 1265.510636]  __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common]
[ 1265.510648]  vb2_core_streamoff+0x24/0xcc [videobuf2_common]
[ 1265.510660]  vb2_ioctl_streamoff+0x5c/0xa8 [videobuf2_v4l2]
[ 1265.510673]  v4l_streamoff+0x24/0x30 [videodev]
[ 1265.510707]  __video_do_ioctl+0x190/0x3f4 [videodev]
[ 1265.510732]  video_usercopy+0x304/0x8c4 [videodev]
[ 1265.510757]  video_ioctl2+0x18/0x34 [videodev]
[ 1265.5…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2024-50175</guid>
    </item>
    <item>
      <title>USN-7301-1 — linux, linux-lowlatency, linux-lowlatency-hwe-6.8 vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-7301-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-lowlatency-hwe-6.8, Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-lowlatency&lt;/p&gt;
&lt;p&gt;Attila Szász discovered that the HFS+ file system implementation in the
Linux Kernel contained a heap overflow vulnerability. An attacker could use
a specially crafted file system image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2025-0927)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM32 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - ACPI drivers;
  - Drivers core;
  - ATA over ethernet (AOE) driver;
  - Network block device driver;
  - TPM device driver;
  - Hardware crypto device drivers;
  - ARM SCMI message protocol;
  - EFI core;
  - GPU drivers;
  - I2C subsystem;
  - I3C subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - IOMMU subsystem;
  - Mailbox framework;
  - Media drivers;
  - Ethernet bonding driver;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NTB driver;
  - PCI subsystem;
  - Alibaba DDR Sub-System Driveway PMU driver;
  - x86 platform drivers;
  - Powercap sysfs driver;
  - Remote Processor subsystem;
  - SCSI subsystem;
  - USB Device Class drivers;
  - vDPA drivers;
  - Virtio Host (VHOST) subsystem;
  - Framebuffer layer;
  - AFS file system;
  - BTRFS file system;
  - File systems infrastructure;
  - Ceph distributed file system;
  - Ext4 f…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-lowlatency-hwe-6.8, Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-lowlatency&lt;/p&gt;
&lt;p&gt;Attila Szász discovered that the HFS+ file system implementation in the
Linux Kernel contained a heap overflow vulnerability. An attacker could use
a specially crafted file system image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2025-0927)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM32 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - ACPI drivers;
  - Drivers core;
  - ATA over ethernet (AOE) driver;
  - Network block device driver;
  - TPM device driver;
  - Hardware crypto device drivers;
  - ARM SCMI message protocol;
  - EFI core;
  - GPU drivers;
  - I2C subsystem;
  - I3C subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - IOMMU subsystem;
  - Mailbox framework;
  - Media drivers;
  - Ethernet bonding driver;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NTB driver;
  - PCI subsystem;
  - Alibaba DDR Sub-System Driveway PMU driver;
  - x86 platform drivers;
  - Powercap sysfs driver;
  - Remote Processor subsystem;
  - SCSI subsystem;
  - USB Device Class drivers;
  - vDPA drivers;
  - Virtio Host (VHOST) subsystem;
  - Framebuffer layer;
  - AFS file system;
  - BTRFS file system;
  - File systems infrastructure;
  - Ceph distributed file system;
  - Ext4 f…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-7301-1</guid>
    </item>
  </channel>
</rss>
