CVE-2024-50175 (GCVE-0-2024-50175)

Vulnerability from cvelistv5 – Published: 2024-11-08 05:23 – Updated: 2026-08-05 11:42
VLAI
Title
media: qcom: camss: Remove use_count guard in stop_streaming
Summary
In the Linux kernel, the following vulnerability has been resolved: media: qcom: camss: Remove use_count guard in stop_streaming 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. 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. If use_count and stream-on count don't agree then stop_streaming() will break as is currently the case and has become apparent when using CAMSS with libcamera's released softisp 0.3. 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. [ 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.510782] v4l2_ioctl+0x40/0x60 [videodev] ... [ 1265.510944] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 0 in active state [ 1265.511175] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 1 in active state [ 1265.511398] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 2 in active st One CAMSS specific way to handle multiple VCs on the same RDI might be: - Reference count each pipeline enable for CSIPHY, CSID, VFE and RDIx. - The video buffers are already associated with msm_vfeN_rdiX so release video buffers when told to do so by stop_streaming. - Only release the power-domains for the CSIPHY, CSID and VFE when their internal refcounts drop. Either way refusing to release video buffers based on use_count is erroneous and should be reverted. The silicon enabling code for selecting VCs is perfectly fine. Its a "known missing feature" that concurrent VCs won't work with CAMSS right now. Initial testing with this code didn't show an error but, SoftISP and "real" usage with Google Hangouts breaks the upstream code pretty quickly, we need to do a partial revert and take another pass at VCs. This commit partially reverts commit 89013969e232 ("media: camss: sm8250: Pipeline starting and stopping for multiple virtual channels")
Severity
7.8 (High)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
5.5 (Medium)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator (v2.0.3)
CWE
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: 89013969e23247661f0514c77f26d60fa083216c , < c2218a82f795dc3d0b6210bcaa3d9c5ca736fcd9 (git)
Affected: 89013969e23247661f0514c77f26d60fa083216c , < a975db8aea152f9907aa53a7f517e557ccb40da3 (git)
Affected: 89013969e23247661f0514c77f26d60fa083216c , < d7d4dde3decef1b5aa1f5c390147f79aae412dee (git)
Affected: 89013969e23247661f0514c77f26d60fa083216c , < 25f18cb1b673220b76a86ebef8e7fb79bd303b27 (git)
Create a notification for this product.
Linux Linux Affected: 6.4
Unaffected: 0 , < 6.4 (semver)
Unaffected: 6.6.55 , ≤ 6.6.* (semver)
Unaffected: 6.10.14 , ≤ 6.10.* (semver)
Unaffected: 6.11.3 , ≤ 6.11.* (semver)
Unaffected: 6.12 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "cvssV3_1": {
              "attackComplexity": "LOW",
              "attackVector": "LOCAL",
              "availabilityImpact": "HIGH",
              "baseScore": 5.5,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "LOW",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
              "version": "3.1"
            }
          },
          {
            "other": {
              "content": {
                "id": "CVE-2024-50175",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2025-10-01T20:19:20.172558Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "problemTypes": [
          {
            "descriptions": [
              {
                "description": "CWE-noinfo Not enough information",
                "lang": "en",
                "type": "CWE"
              }
            ]
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2025-10-01T20:27:10.500Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/media/platform/qcom/camss/camss-video.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "c2218a82f795dc3d0b6210bcaa3d9c5ca736fcd9",
              "status": "affected",
              "version": "89013969e23247661f0514c77f26d60fa083216c",
              "versionType": "git"
            },
            {
              "lessThan": "a975db8aea152f9907aa53a7f517e557ccb40da3",
              "status": "affected",
              "version": "89013969e23247661f0514c77f26d60fa083216c",
              "versionType": "git"
            },
            {
              "lessThan": "d7d4dde3decef1b5aa1f5c390147f79aae412dee",
              "status": "affected",
              "version": "89013969e23247661f0514c77f26d60fa083216c",
              "versionType": "git"
            },
            {
              "lessThan": "25f18cb1b673220b76a86ebef8e7fb79bd303b27",
              "status": "affected",
              "version": "89013969e23247661f0514c77f26d60fa083216c",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/media/platform/qcom/camss/camss-video.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.4"
            },
            {
              "lessThan": "6.4",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.55",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.10.*",
              "status": "unaffected",
              "version": "6.10.14",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.11.*",
              "status": "unaffected",
              "version": "6.11.3",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.12",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.55",
                  "versionStartIncluding": "6.4",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.10.14",
                  "versionStartIncluding": "6.4",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.11.3",
                  "versionStartIncluding": "6.4",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12",
                  "versionStartIncluding": "6.4",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: qcom: camss: Remove use_count guard in stop_streaming\n\nThe use_count check was introduced so that multiple concurrent Raw Data\nInterfaces RDIs could be driven by different virtual channels VCs on the\nCSIPHY input driving the video pipeline.\n\nThis is an invalid use of use_count though as use_count pertains to the\nnumber of times a video entity has been opened by user-space not the number\nof active streams.\n\nIf use_count and stream-on count don\u0027t agree then stop_streaming() will\nbreak as is currently the case and has become apparent when using CAMSS\nwith libcamera\u0027s released softisp 0.3.\n\nThe use of use_count like this is a bit hacky and right now breaks regular\nusage of CAMSS for a single stream case. Stopping qcam results in the splat\nbelow, and then it cannot be started again and any attempts to do so fails\nwith -EBUSY.\n\n[ 1265.509831] WARNING: CPU: 5 PID: 919 at drivers/media/common/videobuf2/videobuf2-core.c:2183 __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common]\n...\n[ 1265.510630] Call trace:\n[ 1265.510636]  __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common]\n[ 1265.510648]  vb2_core_streamoff+0x24/0xcc [videobuf2_common]\n[ 1265.510660]  vb2_ioctl_streamoff+0x5c/0xa8 [videobuf2_v4l2]\n[ 1265.510673]  v4l_streamoff+0x24/0x30 [videodev]\n[ 1265.510707]  __video_do_ioctl+0x190/0x3f4 [videodev]\n[ 1265.510732]  video_usercopy+0x304/0x8c4 [videodev]\n[ 1265.510757]  video_ioctl2+0x18/0x34 [videodev]\n[ 1265.510782]  v4l2_ioctl+0x40/0x60 [videodev]\n...\n[ 1265.510944] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 0 in active state\n[ 1265.511175] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 1 in active state\n[ 1265.511398] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 2 in active st\n\nOne CAMSS specific way to handle multiple VCs on the same RDI might be:\n\n- Reference count each pipeline enable for CSIPHY, CSID, VFE and RDIx.\n- The video buffers are already associated with msm_vfeN_rdiX so\n  release video buffers when told to do so by stop_streaming.\n- Only release the power-domains for the CSIPHY, CSID and VFE when\n  their internal refcounts drop.\n\nEither way refusing to release video buffers based on use_count is\nerroneous and should be reverted. The silicon enabling code for selecting\nVCs is perfectly fine. Its a \"known missing feature\" that concurrent VCs\nwon\u0027t work with CAMSS right now.\n\nInitial testing with this code didn\u0027t show an error but, SoftISP and \"real\"\nusage with Google Hangouts breaks the upstream code pretty quickly, we need\nto do a partial revert and take another pass at VCs.\n\nThis commit partially reverts commit 89013969e232 (\"media: camss: sm8250:\nPipeline starting and stopping for multiple virtual channels\")"
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The vulnerability is reached exclusively through local character-device ioctls on the CAMSS `/dev/videoN` and `/dev/mediaN` nodes (VIDIOC_REQBUFS/QBUF/STREAMON/STREAMOFF, or simply close()). No network or physical-access vector exists.\nAC:L - The attacker controls every precondition: open the video node twice to drive the upstream subdev\u0027s use_count to 2, then STREAMON/STREAMOFF; the early return is then taken deterministically with no race or uncontrolled state. The upstream commit reports this breaking on ordinary single-stream libcamera/qcam usage.\nPR:L - Only an unprivileged local account with access to the camera device nodes is needed \u2014 `video` group membership or a logind seat ACL on desktop/laptop Qualcomm systems, or the camera service context on Android. No capability check exists in `video_open()`, `vb2_ioctl_streamoff()`, or `video_stop_streaming()`.\nUI:N - The attacker performs the entire open/queue/streamon/streamoff/free sequence from its own process. No victim action or cooperating second party is required.\nS:U - The corruption is confined to kernel heap objects and driver state within the same security authority; there is no VM, IOMMU, or sandbox boundary crossed by the bug itself.\nC:H - Skipping `vfe_flush_buffers()` leaves `output-\u003epending_bufs`, `buf[0]/buf[1]` and `last_buffer` dangling after `__vb2_queue_free()`, and the next STREAMON reads `buf-\u003eaddr[0]` out of the freed slab; a use-after-free of this kind gives read access to reclaimed kernel heap contents and can leak them back to userspace via vb2 buffers.\nI:H - `vfe_buf_get_pending()` performs `list_del()` on a freed list node \u2014 a classic unlink write primitive once the slab is resprayed \u2014 and the stale `addr[0]` is programmed as the VFE write-master DMA destination, letting hardware write frame data to an attacker-influenced address. Both yield arbitrary-write potential and control-flow hijack opportunity.\nA:H - The path immediately hits `WARN_ON()` at videobuf2-core.c:2183 (a panic under panic_on_warn), the use-after-free crashes the kernel, and the leaked `media_pipeline` leaves every other video node in the graph permanently returning -EBUSY, disabling the camera subsystem system-wide until reboot."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T11:42:18.585Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/c2218a82f795dc3d0b6210bcaa3d9c5ca736fcd9"
        },
        {
          "url": "https://git.kernel.org/stable/c/a975db8aea152f9907aa53a7f517e557ccb40da3"
        },
        {
          "url": "https://git.kernel.org/stable/c/d7d4dde3decef1b5aa1f5c390147f79aae412dee"
        },
        {
          "url": "https://git.kernel.org/stable/c/25f18cb1b673220b76a86ebef8e7fb79bd303b27"
        }
      ],
      "title": "media: qcom: camss: Remove use_count guard in stop_streaming",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-50175",
    "datePublished": "2024-11-08T05:23:57.808Z",
    "dateReserved": "2024-10-21T19:36:19.963Z",
    "dateUpdated": "2026-08-05T11:42:18.585Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2024-50175",
      "date": "2026-08-05",
      "epss": "0.00231",
      "percentile": "0.14003"
    },
    "fkie_nvd": {
      "configurations": "[{\"nodes\": [{\"operator\": \"OR\", \"negate\": false, \"cpeMatch\": [{\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"6.4\", \"versionEndExcluding\": \"6.6.55\", \"matchCriteriaId\": \"56DA35BA-143D-4269-9914-273743A40222\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"6.7\", \"versionEndExcluding\": \"6.10.14\", \"matchCriteriaId\": \"4C16BCE0-FFA0-4599-BE0A-1FD65101C021\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"6.11\", \"versionEndExcluding\": \"6.11.3\", \"matchCriteriaId\": \"54D9C704-D679-41A7-9C40-10A6B1E7FFE9\"}]}]}]",
      "descriptions": "[{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nmedia: qcom: camss: Remove use_count guard in stop_streaming\\n\\nThe use_count check was introduced so that multiple concurrent Raw Data\\nInterfaces RDIs could be driven by different virtual channels VCs on the\\nCSIPHY input driving the video pipeline.\\n\\nThis is an invalid use of use_count though as use_count pertains to the\\nnumber of times a video entity has been opened by user-space not the number\\nof active streams.\\n\\nIf use_count and stream-on count don\u0027t agree then stop_streaming() will\\nbreak as is currently the case and has become apparent when using CAMSS\\nwith libcamera\u0027s released softisp 0.3.\\n\\nThe use of use_count like this is a bit hacky and right now breaks regular\\nusage of CAMSS for a single stream case. Stopping qcam results in the splat\\nbelow, and then it cannot be started again and any attempts to do so fails\\nwith -EBUSY.\\n\\n[ 1265.509831] WARNING: CPU: 5 PID: 919 at drivers/media/common/videobuf2/videobuf2-core.c:2183 __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common]\\n...\\n[ 1265.510630] Call trace:\\n[ 1265.510636]  __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common]\\n[ 1265.510648]  vb2_core_streamoff+0x24/0xcc [videobuf2_common]\\n[ 1265.510660]  vb2_ioctl_streamoff+0x5c/0xa8 [videobuf2_v4l2]\\n[ 1265.510673]  v4l_streamoff+0x24/0x30 [videodev]\\n[ 1265.510707]  __video_do_ioctl+0x190/0x3f4 [videodev]\\n[ 1265.510732]  video_usercopy+0x304/0x8c4 [videodev]\\n[ 1265.510757]  video_ioctl2+0x18/0x34 [videodev]\\n[ 1265.510782]  v4l2_ioctl+0x40/0x60 [videodev]\\n...\\n[ 1265.510944] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 0 in active state\\n[ 1265.511175] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 1 in active state\\n[ 1265.511398] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 2 in active st\\n\\nOne CAMSS specific way to handle multiple VCs on the same RDI might be:\\n\\n- Reference count each pipeline enable for CSIPHY, CSID, VFE and RDIx.\\n- The video buffers are already associated with msm_vfeN_rdiX so\\n  release video buffers when told to do so by stop_streaming.\\n- Only release the power-domains for the CSIPHY, CSID and VFE when\\n  their internal refcounts drop.\\n\\nEither way refusing to release video buffers based on use_count is\\nerroneous and should be reverted. The silicon enabling code for selecting\\nVCs is perfectly fine. Its a \\\"known missing feature\\\" that concurrent VCs\\nwon\u0027t work with CAMSS right now.\\n\\nInitial testing with this code didn\u0027t show an error but, SoftISP and \\\"real\\\"\\nusage with Google Hangouts breaks the upstream code pretty quickly, we need\\nto do a partial revert and take another pass at VCs.\\n\\nThis commit partially reverts commit 89013969e232 (\\\"media: camss: sm8250:\\nPipeline starting and stopping for multiple virtual channels\\\")\"}, {\"lang\": \"es\", \"value\": \"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: media: qcom: camss: Eliminar la protecci\\u00f3n use_count en stop_streaming La comprobaci\\u00f3n use_count se introdujo para que varias interfaces de datos sin procesar (RDI) simult\\u00e1neas pudieran ser controladas por diferentes canales virtuales VC en la entrada CSIPHY que controlan la canalizaci\\u00f3n de v\\u00eddeo. Sin embargo, este es un uso inv\\u00e1lido de use_count, ya que use_count pertenece a la cantidad de veces que una entidad de v\\u00eddeo ha sido abierta por el espacio de usuario, no a la cantidad de transmisiones activas. Si use_count y stream-on count no coinciden, stop_streaming() se romper\\u00e1, como es el caso actualmente y se ha hecho evidente al usar CAMSS con el softisp 0.3 lanzado por libcamera. El uso de use_count de esta manera es un poco chapucero y, en este momento, interrumpe el uso regular de CAMSS para un solo caso de transmisi\\u00f3n. Detener qcam da como resultado el splat a continuaci\\u00f3n, y luego no se puede iniciar de nuevo y cualquier intento de hacerlo falla con -EBUSY. [ 1265.509831] ADVERTENCIA: CPU: 5 PID: 919 en drivers/media/common/videobuf2/videobuf2-core.c:2183 __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common] ... [ 1265.510630] Rastreo de llamadas: [ 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.510782] v4l2_ioctl+0x40/0x60 [videodev] ... [ 1265.510944] videobuf2_common: error del controlador: la operaci\\u00f3n stop_streaming deja el b\\u00fafer 0 en estado activo [ 1265.511175] videobuf2_common: error del controlador: la operaci\\u00f3n stop_streaming deja el b\\u00fafer 1 en estado activo [ 1265.511398] videobuf2_common: error del controlador: la operaci\\u00f3n stop_streaming deja el buffer 2 en st activo Una forma espec\\u00edfica de CAMSS para manejar m\\u00faltiples VC en el mismo RDI podr\\u00eda ser: - Conteo de referencia de cada canalizaci\\u00f3n habilitada para CSIPHY, CSID, VFE y RDIx. - Los b\\u00faferes de video ya est\\u00e1n asociados con msm_vfeN_rdiX, por lo que libera los b\\u00faferes de video cuando stop_streaming te lo indica. - Solo libera los dominios de energ\\u00eda para CSIPHY, CSID y VFE cuando sus recuentos de referencia internos caen. De cualquier manera, negarse a liberar b\\u00faferes de video seg\\u00fan use_count es err\\u00f3neo y debe revertirse. El c\\u00f3digo de habilitaci\\u00f3n de silicio para seleccionar VC est\\u00e1 perfectamente bien. Es una \\\"caracter\\u00edstica faltante conocida\\\" que los VC simult\\u00e1neos no funcionar\\u00e1n con CAMSS en este momento. Las pruebas iniciales con este c\\u00f3digo no mostraron ning\\u00fan error, pero SoftISP y el uso \\\"real\\\" con Google Hangouts rompen el c\\u00f3digo ascendente con bastante rapidez. Necesitamos hacer una reversi\\u00f3n parcial y volver a pasar por los VC. Esta confirmaci\\u00f3n revierte parcialmente el commit 89013969e232 (\\\"media: camss: sm8250: Pipeline iniciando y deteni\\u00e9ndose para m\\u00faltiples canales virtuales\\\")\"}]",
      "id": "CVE-2024-50175",
      "lastModified": "2024-11-27T20:16:54.450",
      "metrics": "{\"cvssMetricV31\": [{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"cvssData\": {\"version\": \"3.1\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\", \"baseScore\": 5.5, \"baseSeverity\": \"MEDIUM\", \"attackVector\": \"LOCAL\", \"attackComplexity\": \"LOW\", \"privilegesRequired\": \"LOW\", \"userInteraction\": \"NONE\", \"scope\": \"UNCHANGED\", \"confidentialityImpact\": \"NONE\", \"integrityImpact\": \"NONE\", \"availabilityImpact\": \"HIGH\"}, \"exploitabilityScore\": 1.8, \"impactScore\": 3.6}]}",
      "published": "2024-11-08T06:15:14.987",
      "references": "[{\"url\": \"https://git.kernel.org/stable/c/25f18cb1b673220b76a86ebef8e7fb79bd303b27\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/a975db8aea152f9907aa53a7f517e557ccb40da3\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/c2218a82f795dc3d0b6210bcaa3d9c5ca736fcd9\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/d7d4dde3decef1b5aa1f5c390147f79aae412dee\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}]",
      "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "vulnStatus": "Analyzed",
      "weaknesses": "[{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"description\": [{\"lang\": \"en\", \"value\": \"NVD-CWE-noinfo\"}]}]"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-50175\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-11-08T06:15:14.987\",\"lastModified\":\"2026-08-04T11:21:29.197\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nmedia: qcom: camss: Remove use_count guard in stop_streaming\\n\\nThe use_count check was introduced so that multiple concurrent Raw Data\\nInterfaces RDIs could be driven by different virtual channels VCs on the\\nCSIPHY input driving the video pipeline.\\n\\nThis is an invalid use of use_count though as use_count pertains to the\\nnumber of times a video entity has been opened by user-space not the number\\nof active streams.\\n\\nIf use_count and stream-on count don\u0027t agree then stop_streaming() will\\nbreak as is currently the case and has become apparent when using CAMSS\\nwith libcamera\u0027s released softisp 0.3.\\n\\nThe use of use_count like this is a bit hacky and right now breaks regular\\nusage of CAMSS for a single stream case. Stopping qcam results in the splat\\nbelow, and then it cannot be started again and any attempts to do so fails\\nwith -EBUSY.\\n\\n[ 1265.509831] WARNING: CPU: 5 PID: 919 at drivers/media/common/videobuf2/videobuf2-core.c:2183 __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common]\\n...\\n[ 1265.510630] Call trace:\\n[ 1265.510636]  __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common]\\n[ 1265.510648]  vb2_core_streamoff+0x24/0xcc [videobuf2_common]\\n[ 1265.510660]  vb2_ioctl_streamoff+0x5c/0xa8 [videobuf2_v4l2]\\n[ 1265.510673]  v4l_streamoff+0x24/0x30 [videodev]\\n[ 1265.510707]  __video_do_ioctl+0x190/0x3f4 [videodev]\\n[ 1265.510732]  video_usercopy+0x304/0x8c4 [videodev]\\n[ 1265.510757]  video_ioctl2+0x18/0x34 [videodev]\\n[ 1265.510782]  v4l2_ioctl+0x40/0x60 [videodev]\\n...\\n[ 1265.510944] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 0 in active state\\n[ 1265.511175] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 1 in active state\\n[ 1265.511398] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 2 in active st\\n\\nOne CAMSS specific way to handle multiple VCs on the same RDI might be:\\n\\n- Reference count each pipeline enable for CSIPHY, CSID, VFE and RDIx.\\n- The video buffers are already associated with msm_vfeN_rdiX so\\n  release video buffers when told to do so by stop_streaming.\\n- Only release the power-domains for the CSIPHY, CSID and VFE when\\n  their internal refcounts drop.\\n\\nEither way refusing to release video buffers based on use_count is\\nerroneous and should be reverted. The silicon enabling code for selecting\\nVCs is perfectly fine. Its a \\\"known missing feature\\\" that concurrent VCs\\nwon\u0027t work with CAMSS right now.\\n\\nInitial testing with this code didn\u0027t show an error but, SoftISP and \\\"real\\\"\\nusage with Google Hangouts breaks the upstream code pretty quickly, we need\\nto do a partial revert and take another pass at VCs.\\n\\nThis commit partially reverts commit 89013969e232 (\\\"media: camss: sm8250:\\nPipeline starting and stopping for multiple virtual channels\\\")\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: media: qcom: camss: Eliminar la protecci\u00f3n use_count en stop_streaming La comprobaci\u00f3n use_count se introdujo para que varias interfaces de datos sin procesar (RDI) simult\u00e1neas pudieran ser controladas por diferentes canales virtuales VC en la entrada CSIPHY que controlan la canalizaci\u00f3n de v\u00eddeo. Sin embargo, este es un uso inv\u00e1lido de use_count, ya que use_count pertenece a la cantidad de veces que una entidad de v\u00eddeo ha sido abierta por el espacio de usuario, no a la cantidad de transmisiones activas. Si use_count y stream-on count no coinciden, stop_streaming() se romper\u00e1, como es el caso actualmente y se ha hecho evidente al usar CAMSS con el softisp 0.3 lanzado por libcamera. El uso de use_count de esta manera es un poco chapucero y, en este momento, interrumpe el uso regular de CAMSS para un solo caso de transmisi\u00f3n. Detener qcam da como resultado el splat a continuaci\u00f3n, y luego no se puede iniciar de nuevo y cualquier intento de hacerlo falla con -EBUSY. [ 1265.509831] ADVERTENCIA: CPU: 5 PID: 919 en drivers/media/common/videobuf2/videobuf2-core.c:2183 __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common] ... [ 1265.510630] Rastreo de llamadas: [ 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.510782] v4l2_ioctl+0x40/0x60 [videodev] ... [ 1265.510944] videobuf2_common: error del controlador: la operaci\u00f3n stop_streaming deja el b\u00fafer 0 en estado activo [ 1265.511175] videobuf2_common: error del controlador: la operaci\u00f3n stop_streaming deja el b\u00fafer 1 en estado activo [ 1265.511398] videobuf2_common: error del controlador: la operaci\u00f3n stop_streaming deja el buffer 2 en st activo Una forma espec\u00edfica de CAMSS para manejar m\u00faltiples VC en el mismo RDI podr\u00eda ser: - Conteo de referencia de cada canalizaci\u00f3n habilitada para CSIPHY, CSID, VFE y RDIx. - Los b\u00faferes de video ya est\u00e1n asociados con msm_vfeN_rdiX, por lo que libera los b\u00faferes de video cuando stop_streaming te lo indica. - Solo libera los dominios de energ\u00eda para CSIPHY, CSID y VFE cuando sus recuentos de referencia internos caen. De cualquier manera, negarse a liberar b\u00faferes de video seg\u00fan use_count es err\u00f3neo y debe revertirse. El c\u00f3digo de habilitaci\u00f3n de silicio para seleccionar VC est\u00e1 perfectamente bien. Es una \\\"caracter\u00edstica faltante conocida\\\" que los VC simult\u00e1neos no funcionar\u00e1n con CAMSS en este momento. Las pruebas iniciales con este c\u00f3digo no mostraron ning\u00fan error, pero SoftISP y el uso \\\"real\\\" con Google Hangouts rompen el c\u00f3digo ascendente con bastante rapidez. Necesitamos hacer una reversi\u00f3n parcial y volver a pasar por los VC. Esta confirmaci\u00f3n revierte parcialmente el commit 89013969e232 (\\\"media: camss: sm8250: Pipeline iniciando y deteni\u00e9ndose para m\u00faltiples canales virtuales\\\")\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"drivers/media/platform/qcom/camss/camss-video.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"89013969e23247661f0514c77f26d60fa083216c\",\"lessThan\":\"c2218a82f795dc3d0b6210bcaa3d9c5ca736fcd9\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"89013969e23247661f0514c77f26d60fa083216c\",\"lessThan\":\"a975db8aea152f9907aa53a7f517e557ccb40da3\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"89013969e23247661f0514c77f26d60fa083216c\",\"lessThan\":\"d7d4dde3decef1b5aa1f5c390147f79aae412dee\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"89013969e23247661f0514c77f26d60fa083216c\",\"lessThan\":\"25f18cb1b673220b76a86ebef8e7fb79bd303b27\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"drivers/media/platform/qcom/camss/camss-video.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"6.4\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"6.4\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.6.55\",\"lessThanOrEqual\":\"6.6.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.10.14\",\"lessThanOrEqual\":\"6.10.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.11.3\",\"lessThanOrEqual\":\"6.11.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.12\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":7.8,\"baseSeverity\":\"HIGH\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":5.9},{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":3.6},{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":3.6}],\"ssvcV203\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"ssvcData\":{\"timestamp\":\"2025-10-01T20:19:20.172558Z\",\"id\":\"CVE-2024-50175\",\"options\":[{\"exploitation\":\"none\"},{\"automatable\":\"no\"},{\"technicalImpact\":\"partial\"}],\"role\":\"CISA Coordinator\",\"version\":\"2.0.3\"}}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"NVD-CWE-noinfo\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.4\",\"versionEndExcluding\":\"6.6.55\",\"matchCriteriaId\":\"56DA35BA-143D-4269-9914-273743A40222\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.7\",\"versionEndExcluding\":\"6.10.14\",\"matchCriteriaId\":\"4C16BCE0-FFA0-4599-BE0A-1FD65101C021\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.11\",\"versionEndExcluding\":\"6.11.3\",\"matchCriteriaId\":\"54D9C704-D679-41A7-9C40-10A6B1E7FFE9\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/25f18cb1b673220b76a86ebef8e7fb79bd303b27\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/a975db8aea152f9907aa53a7f517e557ccb40da3\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/c2218a82f795dc3d0b6210bcaa3d9c5ca736fcd9\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/d7d4dde3decef1b5aa1f5c390147f79aae412dee\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}",
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-08-04T14:17:57+00:00",
      "cve": "CVE-2024-50175",
      "id": "CVE-2024-50175",
      "initial_release_date": "2024-11-08T00:00:00+00:00",
      "product_status:known_not_affected": "198",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: media: qcom: camss: Remove use_count guard in stop_streaming",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-50175.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-07-25T01:27:07Z",
      "cve": "CVE-2024-50175",
      "id": "CVE-2024-50175",
      "initial_release_date": "2024-11-09T03:49:19Z",
      "product_status:known_affected": "394",
      "product_status:known_not_affected": "316",
      "product_status:recommended": "316",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2024-50175",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2024-50175.json",
      "version": "46"
    },
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 5.5, \"attackVector\": \"LOCAL\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\", \"integrityImpact\": \"NONE\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"HIGH\", \"privilegesRequired\": \"LOW\", \"confidentialityImpact\": \"NONE\"}}, {\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-50175\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2025-10-01T20:19:20.172558Z\"}}}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"description\": \"CWE-noinfo Not enough information\"}]}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2025-10-01T15:19:41.112Z\"}}], \"cna\": {\"title\": \"media: qcom: camss: Remove use_count guard in stop_streaming\", \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"89013969e23247661f0514c77f26d60fa083216c\", \"lessThan\": \"c2218a82f795dc3d0b6210bcaa3d9c5ca736fcd9\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"89013969e23247661f0514c77f26d60fa083216c\", \"lessThan\": \"a975db8aea152f9907aa53a7f517e557ccb40da3\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"89013969e23247661f0514c77f26d60fa083216c\", \"lessThan\": \"d7d4dde3decef1b5aa1f5c390147f79aae412dee\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"89013969e23247661f0514c77f26d60fa083216c\", \"lessThan\": \"25f18cb1b673220b76a86ebef8e7fb79bd303b27\", \"versionType\": \"git\"}], \"programFiles\": [\"drivers/media/platform/qcom/camss/camss-video.c\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"6.4\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"6.4\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"6.6.55\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.6.*\"}, {\"status\": \"unaffected\", \"version\": \"6.10.14\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.10.*\"}, {\"status\": \"unaffected\", \"version\": \"6.11.3\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.11.*\"}, {\"status\": \"unaffected\", \"version\": \"6.12\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"drivers/media/platform/qcom/camss/camss-video.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/c2218a82f795dc3d0b6210bcaa3d9c5ca736fcd9\"}, {\"url\": \"https://git.kernel.org/stable/c/a975db8aea152f9907aa53a7f517e557ccb40da3\"}, {\"url\": \"https://git.kernel.org/stable/c/d7d4dde3decef1b5aa1f5c390147f79aae412dee\"}, {\"url\": \"https://git.kernel.org/stable/c/25f18cb1b673220b76a86ebef8e7fb79bd303b27\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nmedia: qcom: camss: Remove use_count guard in stop_streaming\\n\\nThe use_count check was introduced so that multiple concurrent Raw Data\\nInterfaces RDIs could be driven by different virtual channels VCs on the\\nCSIPHY input driving the video pipeline.\\n\\nThis is an invalid use of use_count though as use_count pertains to the\\nnumber of times a video entity has been opened by user-space not the number\\nof active streams.\\n\\nIf use_count and stream-on count don\u0027t agree then stop_streaming() will\\nbreak as is currently the case and has become apparent when using CAMSS\\nwith libcamera\u0027s released softisp 0.3.\\n\\nThe use of use_count like this is a bit hacky and right now breaks regular\\nusage of CAMSS for a single stream case. Stopping qcam results in the splat\\nbelow, and then it cannot be started again and any attempts to do so fails\\nwith -EBUSY.\\n\\n[ 1265.509831] WARNING: CPU: 5 PID: 919 at drivers/media/common/videobuf2/videobuf2-core.c:2183 __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common]\\n...\\n[ 1265.510630] Call trace:\\n[ 1265.510636]  __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common]\\n[ 1265.510648]  vb2_core_streamoff+0x24/0xcc [videobuf2_common]\\n[ 1265.510660]  vb2_ioctl_streamoff+0x5c/0xa8 [videobuf2_v4l2]\\n[ 1265.510673]  v4l_streamoff+0x24/0x30 [videodev]\\n[ 1265.510707]  __video_do_ioctl+0x190/0x3f4 [videodev]\\n[ 1265.510732]  video_usercopy+0x304/0x8c4 [videodev]\\n[ 1265.510757]  video_ioctl2+0x18/0x34 [videodev]\\n[ 1265.510782]  v4l2_ioctl+0x40/0x60 [videodev]\\n...\\n[ 1265.510944] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 0 in active state\\n[ 1265.511175] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 1 in active state\\n[ 1265.511398] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 2 in active st\\n\\nOne CAMSS specific way to handle multiple VCs on the same RDI might be:\\n\\n- Reference count each pipeline enable for CSIPHY, CSID, VFE and RDIx.\\n- The video buffers are already associated with msm_vfeN_rdiX so\\n  release video buffers when told to do so by stop_streaming.\\n- Only release the power-domains for the CSIPHY, CSID and VFE when\\n  their internal refcounts drop.\\n\\nEither way refusing to release video buffers based on use_count is\\nerroneous and should be reverted. The silicon enabling code for selecting\\nVCs is perfectly fine. Its a \\\"known missing feature\\\" that concurrent VCs\\nwon\u0027t work with CAMSS right now.\\n\\nInitial testing with this code didn\u0027t show an error but, SoftISP and \\\"real\\\"\\nusage with Google Hangouts breaks the upstream code pretty quickly, we need\\nto do a partial revert and take another pass at VCs.\\n\\nThis commit partially reverts commit 89013969e232 (\\\"media: camss: sm8250:\\nPipeline starting and stopping for multiple virtual channels\\\")\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.6.55\", \"versionStartIncluding\": \"6.4\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.10.14\", \"versionStartIncluding\": \"6.4\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.11.3\", \"versionStartIncluding\": \"6.4\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.12\", \"versionStartIncluding\": \"6.4\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2025-05-04T09:47:57.266Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2024-50175\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2025-10-01T20:27:10.500Z\", \"dateReserved\": \"2024-10-21T19:36:19.963Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-11-08T05:23:57.808Z\", \"assignerShortName\": \"Linux\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.1"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.