CVE-2024-50175
Vulnerability from cvelistv5
Published
2024-11-08 05:23
Modified
2024-12-19 09:34
Severity ?
EPSS score ?
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")
References
Impacted products
{
"containers": {
"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"
}
]
}
],
"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\")"
}
],
"providerMetadata": {
"dateUpdated": "2024-12-19T09:34:40.275Z",
"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-5f407fcff5a0"
}
}
},
"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": "2024-12-19T09:34:40.275Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.1",
"meta": {
"nvd": "{\"cve\":{\"id\":\"CVE-2024-50175\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-11-08T06:15:14.987\",\"lastModified\":\"2024-11-27T20:16:54.450\",\"vulnStatus\":\"Analyzed\",\"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\\\")\"}],\"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}]},\"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\"]}]}}"
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.