mirror of
https://github.com/fkie-cad/nvd-json-data-feeds.git
synced 2025-06-01 19:21:37 +00:00
36 lines
3.3 KiB
JSON
36 lines
3.3 KiB
JSON
{
|
|
"id": "CVE-2024-26821",
|
|
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
|
"published": "2024-04-17T10:15:08.917",
|
|
"lastModified": "2024-04-17T12:48:07.510",
|
|
"vulnStatus": "Awaiting Analysis",
|
|
"descriptions": [
|
|
{
|
|
"lang": "en",
|
|
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nfs: relax mount_setattr() permission checks\n\nWhen we added mount_setattr() I added additional checks compared to the\nlegacy do_reconfigure_mnt() and do_change_type() helpers used by regular\nmount(2). If that mount had a parent then verify that the caller and the\nmount namespace the mount is attached to match and if not make sure that\nit's an anonymous mount.\n\nThe real rootfs falls into neither category. It is neither an anoymous\nmount because it is obviously attached to the initial mount namespace\nbut it also obviously doesn't have a parent mount. So that means legacy\nmount(2) allows changing mount properties on the real rootfs but\nmount_setattr(2) blocks this. I never thought much about this but of\ncourse someone on this planet of earth changes properties on the real\nrootfs as can be seen in [1].\n\nSince util-linux finally switched to the new mount api in 2.39 not so\nlong ago it also relies on mount_setattr() and that surfaced this issue\nwhen Fedora 39 finally switched to it. Fix this."
|
|
},
|
|
{
|
|
"lang": "es",
|
|
"value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: fs: relajar las comprobaciones de permisos de mount_setattr() Cuando agregamos mount_setattr(), agregu\u00e9 comprobaciones adicionales en comparaci\u00f3n con los ayudantes heredados do_reconfigure_mnt() y do_change_type() utilizados por el mount(2) normal. Si ese montaje ten\u00eda un padre, verifique que la persona que llama y el espacio de nombres del montaje coincidan y, de lo contrario, aseg\u00farese de que sea un montaje an\u00f3nimo. Los rootfs reales no entran en ninguna de las dos categor\u00edas. No es un montaje an\u00f3nimo porque obviamente est\u00e1 adjunto al espacio de nombres de montaje inicial pero obviamente tampoco tiene un montaje principal. Eso significa que el montaje heredado (2) permite cambiar las propiedades de montaje en los rootfs reales, pero mount_setattr (2) bloquea esto. Nunca pens\u00e9 mucho en esto pero, por supuesto, alguien en este planeta tierra cambia las propiedades de las ra\u00edces reales como se puede ver en [1]. Dado que util-linux finalmente cambi\u00f3 a la nueva API de montaje en 2.39 no hace mucho, tambi\u00e9n depende de mount_setattr() y surgi\u00f3 este problema cuando Fedora 39 finalmente cambi\u00f3 a ella. Arregla esto."
|
|
}
|
|
],
|
|
"metrics": {},
|
|
"references": [
|
|
{
|
|
"url": "https://git.kernel.org/stable/c/2a7a31e1fb9717845d9d5e2a8c6e48848147801e",
|
|
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
|
},
|
|
{
|
|
"url": "https://git.kernel.org/stable/c/31f71f2d7a081fc6c6bdf06865beedf6db5b0ca4",
|
|
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
|
},
|
|
{
|
|
"url": "https://git.kernel.org/stable/c/46f5ab762d048dad224436978315cbc2fa79c630",
|
|
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
|
},
|
|
{
|
|
"url": "https://git.kernel.org/stable/c/95de4ad173ca0e61034f3145d66917970961c210",
|
|
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
|
}
|
|
]
|
|
} |