CVE-2023-54058

Unknown

Description

In the Linux kernel, the following vulnerability has been resolved: firmware: arm_ffa: Check if ffa_driver remove is present before executing Currently ffa_drv->remove() is called unconditionally from ffa_device_remove(). Since the driver registration doesn't check for it and allows it to be registered without .remove callback, we need to check for the presence of it before executing it from ffa_device_remove() to above a NULL pointer dereference like the one below: | Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 | Mem abort info: | ESR = 0x0000000086000004 | EC = 0x21: IABT (current EL), IL = 32 bits | SET = 0, FnV = 0 | EA = 0, S1PTW = 0 | FSC = 0x04: level 0 translation fault | user pgtable: 4k pages, 48-bit VAs, pgdp=0000000881cc8000 | [0000000000000000] pgd=0000000000000000, p4d=0000000000000000 | Internal error: Oops: 0000000086000004 [#1] PREEMPT SMP | CPU: 3 PID: 130 Comm: rmmod Not tainted 6.3.0-rc7 #6 | Hardware name: FVP Base RevC (DT) | pstate: 63402809 (nZCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=-c) | pc : 0x0 | lr : ffa_device_remove+0x20/0x2c | Call trace: | 0x0 | device_release_driver_internal+0x16c/0x260 | driver_detach+0x90/0xd0 | bus_remove_driver+0xdc/0x11c | driver_unregister+0x30/0x54 | ffa_driver_unregister+0x14/0x20 | cleanup_module+0x18/0xeec | __arm64_sys_delete_module+0x234/0x378 | invoke_syscall+0x40/0x108 | el0_svc_common+0xb4/0xf0 | do_el0_svc+0x30/0xa4 | el0_svc+0x2c/0x7c | el0t_64_sync_handler+0x84/0xf0 | el0t_64_sync+0x190/0x194

SeverityUnknown
CVSS—
Exploit probability—
ProductLinux
PublishedDec 24, 2025
First seenDec 24, 2025

How to fix

Update
  • Linux Linux6a26c62625c59b8dd7f52c518cb4f60a63470a0e, ad73dc7263ea90302d6c7eeb7e9f7cbcfa0b0617, 48399c297c46b4c8e77ebcf071bb586a42d0ca4e, b71b55248a580e9c9befc4ae060539f1f8e477da, 5.15 or later

Affected products

ProductAffected versionsFixed in
Linux Linux244f5d597e1ea519c2085fbd9819458688775e42 ≤ v < 6a26c62625c59b8dd7f52c518cb4f60a63470a0e, 244f5d597e1ea519c2085fbd9819458688775e42 ≤ v < ad73dc7263ea90302d6c7eeb7e9f7cbcfa0b0617, 244f5d597e1ea519c2085fbd9819458688775e42 ≤ v < 48399c297c46b4c8e77ebcf071bb586a42d0ca4e, 244f5d597e1ea519c2085fbd9819458688775e42 ≤ v < b71b55248a580e9c9befc4ae060539f1f8e477da, 06560ba731e2775441c6dc9f0bf39f9f3606fbb7, 5.14.14 ≤ v < 5.15, 5.156a26c62625c59b8dd7f52c518cb4f60a63470a0e, ad73dc7263ea90302d6c7eeb7e9f7cbcfa0b0617, 48399c297c46b4c8e77ebcf071bb586a42d0ca4e, b71b55248a580e9c9befc4ae060539f1f8e477da, 5.15

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.