fkie_cve-2024-56585
Vulnerability from fkie_nvd
Published
2024-12-27 15:15
Modified
2024-12-27 15:15
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved:
LoongArch: Fix sleeping in atomic context for PREEMPT_RT
Commit bab1c299f3945ffe79 ("LoongArch: Fix sleeping in atomic context in
setup_tlb_handler()") changes the gfp flag from GFP_KERNEL to GFP_ATOMIC
for alloc_pages_node(). However, for PREEMPT_RT kernels we can still get
a "sleeping in atomic context" error:
[ 0.372259] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48
[ 0.372266] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 0, name: swapper/1
[ 0.372268] preempt_count: 1, expected: 0
[ 0.372270] RCU nest depth: 1, expected: 1
[ 0.372272] 3 locks held by swapper/1/0:
[ 0.372274] #0: 900000000c9f5e60 (&pcp->lock){+.+.}-{3:3}, at: get_page_from_freelist+0x524/0x1c60
[ 0.372294] #1: 90000000087013b8 (rcu_read_lock){....}-{1:3}, at: rt_spin_trylock+0x50/0x140
[ 0.372305] #2: 900000047fffd388 (&zone->lock){+.+.}-{3:3}, at: __rmqueue_pcplist+0x30c/0xea0
[ 0.372314] irq event stamp: 0
[ 0.372316] hardirqs last enabled at (0): [<0000000000000000>] 0x0
[ 0.372322] hardirqs last disabled at (0): [<9000000005947320>] copy_process+0x9c0/0x26e0
[ 0.372329] softirqs last enabled at (0): [<9000000005947320>] copy_process+0x9c0/0x26e0
[ 0.372335] softirqs last disabled at (0): [<0000000000000000>] 0x0
[ 0.372341] CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 6.12.0-rc7+ #1891
[ 0.372346] Hardware name: Loongson Loongson-3A5000-7A1000-1w-CRB/Loongson-LS3A5000-7A1000-1w-CRB, BIOS vUDK2018-LoongArch-V2.0.0-prebeta9 10/21/2022
[ 0.372349] Stack : 0000000000000089 9000000005a0db9c 90000000071519c8 9000000100388000
[ 0.372486] 900000010038b890 0000000000000000 900000010038b898 9000000007e53788
[ 0.372492] 900000000815bcc8 900000000815bcc0 900000010038b700 0000000000000001
[ 0.372498] 0000000000000001 4b031894b9d6b725 00000000055ec000 9000000100338fc0
[ 0.372503] 00000000000000c4 0000000000000001 000000000000002d 0000000000000003
[ 0.372509] 0000000000000030 0000000000000003 00000000055ec000 0000000000000003
[ 0.372515] 900000000806d000 9000000007e53788 00000000000000b0 0000000000000004
[ 0.372521] 0000000000000000 0000000000000000 900000000c9f5f10 0000000000000000
[ 0.372526] 90000000076f12d8 9000000007e53788 9000000005924778 0000000000000000
[ 0.372532] 00000000000000b0 0000000000000004 0000000000000000 0000000000070000
[ 0.372537] ...
[ 0.372540] Call Trace:
[ 0.372542] [<9000000005924778>] show_stack+0x38/0x180
[ 0.372548] [<90000000071519c4>] dump_stack_lvl+0x94/0xe4
[ 0.372555] [<900000000599b880>] __might_resched+0x1a0/0x260
[ 0.372561] [<90000000071675cc>] rt_spin_lock+0x4c/0x140
[ 0.372565] [<9000000005cbb768>] __rmqueue_pcplist+0x308/0xea0
[ 0.372570] [<9000000005cbed84>] get_page_from_freelist+0x564/0x1c60
[ 0.372575] [<9000000005cc0d98>] __alloc_pages_noprof+0x218/0x1820
[ 0.372580] [<900000000593b36c>] tlb_init+0x1ac/0x298
[ 0.372585] [<9000000005924b74>] per_cpu_trap_init+0x114/0x140
[ 0.372589] [<9000000005921964>] cpu_probe+0x4e4/0xa60
[ 0.372592] [<9000000005934874>] start_secondary+0x34/0xc0
[ 0.372599] [<900000000715615c>] smpboot_entry+0x64/0x6c
This is because in PREEMPT_RT kernels normal spinlocks are replaced by
rt spinlocks and rt_spin_lock() will cause sleeping. Fix it by disabling
NUMA optimization completely for PREEMPT_RT kernels.
References
Impacted products
Vendor | Product | Version |
---|
{ "cveTags": [], "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: Fix sleeping in atomic context for PREEMPT_RT\n\nCommit bab1c299f3945ffe79 (\"LoongArch: Fix sleeping in atomic context in\nsetup_tlb_handler()\") changes the gfp flag from GFP_KERNEL to GFP_ATOMIC\nfor alloc_pages_node(). However, for PREEMPT_RT kernels we can still get\na \"sleeping in atomic context\" error:\n\n[ 0.372259] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48\n[ 0.372266] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 0, name: swapper/1\n[ 0.372268] preempt_count: 1, expected: 0\n[ 0.372270] RCU nest depth: 1, expected: 1\n[ 0.372272] 3 locks held by swapper/1/0:\n[ 0.372274] #0: 900000000c9f5e60 (\u0026pcp-\u003elock){+.+.}-{3:3}, at: get_page_from_freelist+0x524/0x1c60\n[ 0.372294] #1: 90000000087013b8 (rcu_read_lock){....}-{1:3}, at: rt_spin_trylock+0x50/0x140\n[ 0.372305] #2: 900000047fffd388 (\u0026zone-\u003elock){+.+.}-{3:3}, at: __rmqueue_pcplist+0x30c/0xea0\n[ 0.372314] irq event stamp: 0\n[ 0.372316] hardirqs last enabled at (0): [\u003c0000000000000000\u003e] 0x0\n[ 0.372322] hardirqs last disabled at (0): [\u003c9000000005947320\u003e] copy_process+0x9c0/0x26e0\n[ 0.372329] softirqs last enabled at (0): [\u003c9000000005947320\u003e] copy_process+0x9c0/0x26e0\n[ 0.372335] softirqs last disabled at (0): [\u003c0000000000000000\u003e] 0x0\n[ 0.372341] CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 6.12.0-rc7+ #1891\n[ 0.372346] Hardware name: Loongson Loongson-3A5000-7A1000-1w-CRB/Loongson-LS3A5000-7A1000-1w-CRB, BIOS vUDK2018-LoongArch-V2.0.0-prebeta9 10/21/2022\n[ 0.372349] Stack : 0000000000000089 9000000005a0db9c 90000000071519c8 9000000100388000\n[ 0.372486] 900000010038b890 0000000000000000 900000010038b898 9000000007e53788\n[ 0.372492] 900000000815bcc8 900000000815bcc0 900000010038b700 0000000000000001\n[ 0.372498] 0000000000000001 4b031894b9d6b725 00000000055ec000 9000000100338fc0\n[ 0.372503] 00000000000000c4 0000000000000001 000000000000002d 0000000000000003\n[ 0.372509] 0000000000000030 0000000000000003 00000000055ec000 0000000000000003\n[ 0.372515] 900000000806d000 9000000007e53788 00000000000000b0 0000000000000004\n[ 0.372521] 0000000000000000 0000000000000000 900000000c9f5f10 0000000000000000\n[ 0.372526] 90000000076f12d8 9000000007e53788 9000000005924778 0000000000000000\n[ 0.372532] 00000000000000b0 0000000000000004 0000000000000000 0000000000070000\n[ 0.372537] ...\n[ 0.372540] Call Trace:\n[ 0.372542] [\u003c9000000005924778\u003e] show_stack+0x38/0x180\n[ 0.372548] [\u003c90000000071519c4\u003e] dump_stack_lvl+0x94/0xe4\n[ 0.372555] [\u003c900000000599b880\u003e] __might_resched+0x1a0/0x260\n[ 0.372561] [\u003c90000000071675cc\u003e] rt_spin_lock+0x4c/0x140\n[ 0.372565] [\u003c9000000005cbb768\u003e] __rmqueue_pcplist+0x308/0xea0\n[ 0.372570] [\u003c9000000005cbed84\u003e] get_page_from_freelist+0x564/0x1c60\n[ 0.372575] [\u003c9000000005cc0d98\u003e] __alloc_pages_noprof+0x218/0x1820\n[ 0.372580] [\u003c900000000593b36c\u003e] tlb_init+0x1ac/0x298\n[ 0.372585] [\u003c9000000005924b74\u003e] per_cpu_trap_init+0x114/0x140\n[ 0.372589] [\u003c9000000005921964\u003e] cpu_probe+0x4e4/0xa60\n[ 0.372592] [\u003c9000000005934874\u003e] start_secondary+0x34/0xc0\n[ 0.372599] [\u003c900000000715615c\u003e] smpboot_entry+0x64/0x6c\n\nThis is because in PREEMPT_RT kernels normal spinlocks are replaced by\nrt spinlocks and rt_spin_lock() will cause sleeping. Fix it by disabling\nNUMA optimization completely for PREEMPT_RT kernels." }, { "lang": "es", "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: LoongArch: Fix sleeping in atomic context for PREEMPT_RT el commit bab1c299f3945ffe79 (\"LoongArch: Fix sleeping in atomic context in setup_tlb_handler()\") cambia el indicador gfp de GFP_KERNEL a GFP_ATOMIC para alloc_pages_node(). Sin embargo, para los n\u00facleos PREEMPT_RT a\u00fan podemos obtener un error de \"durmiendo en contexto at\u00f3mico\": [ 0.372259] ERROR: funci\u00f3n de suspensi\u00f3n llamada desde un contexto no v\u00e1lido en kernel/locking/spinlock_rt.c:48 [ 0.372266] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 0, name: swapper/1 [ 0.372268] preempt_count: 1, esperado: 0 [ 0.372270] Profundidad de anidamiento de RCU: 1, esperado: 1 [ 0.372272] 3 bloqueos mantenidos por swapper/1/0: [ 0.372274] #0: 900000000c9f5e60 (\u0026amp;pcp-\u0026gt;lock){+.+.}-{3:3}, en: get_page_from_freelist+0x524/0x1c60 [ 0.372294] #1: 90000000087013b8 (rcu_read_lock){....}-{1:3}, en: rt_spin_trylock+0x50/0x140 [ 0.372305] #2: 900000047fffd388 (\u0026amp;zone-\u0026gt;lock){+.+.}-{3:3}, en: __rmqueue_pcplist+0x30c/0xea0 [ 0.372314] marca de evento irq: 0 [ 0.372316] hardirqs habilitado por \u00faltima vez en (0): [\u0026lt;000000000000000\u0026gt;] 0x0 [ 0.372322] hardirqs deshabilitado por \u00faltima vez en (0): [\u0026lt;9000000005947320\u0026gt;] copy_process+0x9c0/0x26e0 [ 0.372329] softirqs se habilit\u00f3 por \u00faltima vez en (0): [\u0026lt;9000000005947320\u0026gt;] copy_process+0x9c0/0x26e0 [ 0.372335] softirqs se deshabilit\u00f3 por \u00faltima vez en (0): [\u0026lt;000000000000000\u0026gt;] 0x0 [ 0.372341] CPU: 1 UID: 0 PID: 0 Comm: swapper/1 No contaminado 6.12.0-rc7+ #1891 [ 0.372346] Nombre del hardware: Loongson Loongson-3A5000-7A1000-1w-CRB/Loongson-LS3A5000-7A1000-1w-CRB, BIOS vUDK2018-LoongArch-V2.0.0-prebeta9 21/10/2022 [0.372349] Pila: 0000000000000089 9000000005a0db9c 90000000071519c8 9000000100388000 [ 0.372486] 900000010038b890 00000000000000000 900000010038b898 9000000007e53788 [ 0,372492] 900000000815bcc8 900000000815bcc0 900000010038b700 0000000000000001 [ 0,372498] 000000000000001 4b031894b9d6b725 00000000055ec000 9000000100338fc0 [ 0,372503] 00000000000000c4 000000000000001 00000000000002d 0000000000000003 [ 0,372509] 0000000000000030 0000000000000003 000000000055ec000 0000000000000003 [ 0.372515] 900000000806d000 9000000007e53788 00000000000000b0 0000000000000004 [ 0.372521] 000000000000000 000000000000000 900000000c9f5f10 000000000000000 [ 0.372526] 90000000076f12d8 9000000007e53788 9000000005924778 0000000000000000 [ 0.372532] 00000000000000b0 0000000000000004 0000000000000000 0000000000070000 [ 0.372537] ... [ 0.372540] Seguimiento de llamadas: [ 0.372542] [\u0026lt;9000000005924778\u0026gt;] show_stack+0x38/0x180 [ 0.372548] [\u0026lt;90000000071519c4\u0026gt;] nivel_pila_volcado+0x94/0xe4 [ 0.372555] [\u0026lt;900000000599b880\u0026gt;] __might_resched+0x1a0/0x260 [ 0.372561] [\u0026lt;90000000071675cc\u0026gt;] bloqueo_giro_rt+0x4c/0x140 [ 0.372565] [\u0026lt;9000000005cbb768\u0026gt;] __rmqueue_pcplist+0x308/0xea0 [ 0.372570] [\u0026lt;9000000005cbed84\u0026gt;] obtener_p\u00e1gina_de_lista_libre+0x564/0x1c60 [ 0.372575] [\u0026lt;9000000005cc0d98\u0026gt;] __alloc_pages_noprof+0x218/0x1820 [ 0.372580] [\u0026lt;900000000593b36c\u0026gt;] tlb_init+0x1ac/0x298 [ 0.372585] [\u0026lt;9000000005924b74\u0026gt;] por_cpu_trap_init+0x114/0x140 [ 0.372589] [\u0026lt;9000000005921964\u0026gt;] cpu_probe+0x4e4/0xa60 [ 0.372592] [\u0026lt;9000000005934874\u0026gt;] inicio_secundario+0x34/0xc0 [ 0.372599] [\u0026lt;900000000715615c\u0026gt;] smpboot_entry+0x64/0x6c Esto se debe a que en los n\u00facleos PREEMPT_RT los spinlocks normales se reemplazan por spinlocks rt y rt_spin_lock() provocar\u00e1 un estado de suspensi\u00f3n. Solucione este problema deshabilitando por completo la optimizaci\u00f3n NUMA para los n\u00facleos PREEMPT_RT." } ], "id": "CVE-2024-56585", "lastModified": "2024-12-27T15:15:17.677", "metrics": {}, "published": "2024-12-27T15:15:17.677", "references": [ { "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/08715b741f9b2a925d6485491e4907f3b29bac70" }, { "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/6575e0867bd478a5d7ef1783ca1e73160807d238" }, { "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/88fd2b70120d52c1010257d36776876941375490" }, { "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/c5f89458a2ea0800866b9fc690d3fa8367dc8f8d" } ], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Awaiting Analysis" }
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.