scsi: ufs: core: Cancel RTC work during ufshcd_remove()
In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Cancel RTC work during ufshcd_remove() Currently, RTC work is only cancelled during __ufshcd_wl_suspend(). When ufshcd is removed in ufshcd_remove(), RTC work is not cancelled. Due to this, any further trigger of the RTC work after ufshcd_remove() would result in a NULL pointer dereference as below: Unable to handle kernel NULL pointer dereference at virtual address 00000000000002a4 Workqueue: events ufshcd_rtc_work Call trace: _raw_spin_lock_irqsave+0x34/0x8c pm_runtime_get_if_active+0x24/0xb4 ufshcd_rtc_work+0x124/0x19c process_scheduled_works+0x18c/0x2d8 worker_thread+0x144/0x280 kthread+0x11c/0x128 ret_from_fork+0x10/0x20 Since RTC work accesses the ufshcd internal structures, it should be cancelled when ufshcd is removed. So do that in ufshcd_remove(), as per the order in ufshcd_init().
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.12.5
- CVEs
- CVE-2024-56621
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 6 Nov 2026, 00:32 UTC · Revision 1
Source evidence
scsi: ufs: core: Cancel RTC work during ufshcd_remove()
core-osv · Original sourcePublished 27 Dec 2024, 14:51 UTC
In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Cancel RTC work during ufshcd_remove() Currently, RTC work is only cancelled during __ufshcd_wl_suspend(). When ufshcd is removed in ufshcd_remove(), RTC work is not cancelled. Due to this, any further trigger of the RTC work after ufshcd_remove() would result in a NULL pointer dereference as below: Unable to handle kernel NULL pointer dereference at virtual address 00000000000002a4 Workqueue: events ufshcd_rtc_work Call trace: _raw_spin_lock_irqsave+0x34/0x8c pm_runtime_get_if_active+0x24/0xb4 ufshcd_rtc_work+0x124/0x19c process_scheduled_works+0x18c/0x2d8 worker_thread+0x144/0x280 kthread+0x11c/0x128 ret_from_fork+0x10/0x20 Since RTC work accesses the ufshcd internal structures, it should be cancelled when ufshcd is removed. So do that in ufshcd_remove(), as per the order in ufshcd_init().
osv:CVE-2024-56621
Kernel
Fixed versions: 6.12.5
Complete source record
{
"id": "cf5bca9b6df998b7adc3f0562926848b5cb9549bb170193afae2cfc729ab093c",
"url": "https://osv.dev/vulnerability/CVE-2024-56621",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "scsi: ufs: core: Cancel RTC work during ufshcd_remove()",
"summary": "In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Cancel RTC work during ufshcd_remove() Currently, RTC work is only cancelled during __ufshcd_wl_suspend(). When ufshcd is removed in ufshcd_remove(), RTC work is not cancelled. Due to this, any further trigger of the RTC work after ufshcd_remove() would result in a NULL pointer dereference as below: Unable to handle kernel NULL pointer dereference at virtual address 00000000000002a4 Workqueue: events ufshcd_rtc_work Call trace: _raw_spin_lock_irqsave+0x34/0x8c pm_runtime_get_if_active+0x24/0xb4 ufshcd_rtc_work+0x124/0x19c process_scheduled_works+0x18c/0x2d8 worker_thread+0x144/0x280 kthread+0x11c/0x128 ret_from_fork+0x10/0x20 Since RTC work accesses the ufshcd internal structures, it should be cancelled when ufshcd is removed. So do that in ufshcd_remove(), as per the order in ufshcd_init().",
"evidence": "osv:CVE-2024-56621",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.12.5",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2024-56621",
"aliases": [
"CVE-2024-56621"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "06701a545e9a3c4e007cff6872a074bf97c40619"
},
{
"fixed": "57479e37d3f69efee2f0678568274db773284bc8"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "6bf999e0eb41850d5c857102535d5c53b2ede224"
},
{
"fixed": "2e7a3bb0331efb292e0fb022c36bc592137f0520"
},
{
"fixed": "1695c4361d35b7bdadd7b34f99c9c07741e181e5"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-56621.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.8.0"
},
{
"fixed": "6.12.5"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-56621.json"
}
}
],
"modified": "2026-10-28T02:30:45.795249669Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/1695c4361d35b7bdadd7b34f99c9c07741e181e5",
"https://git.kernel.org/stable/c/2e7a3bb0331efb292e0fb022c36bc592137f0520",
"https://git.kernel.org/stable/c/57479e37d3f69efee2f0678568274db773284bc8",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/56xxx/CVE-2024-56621.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-56621",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/56xxx/CVE-2024-56621.json"
}
},
"related_cves": [
{
"value": "CVE-2024-56621",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 513507,
"published_at": "2024-12-27T14:51:24.948+00:00"
}