block: don't delete queue kobject before its children
In the Linux kernel, the following vulnerability has been resolved: block: don't delete queue kobject before its children kobjects aren't supposed to be deleted before their child kobjects are deleted. Apparently this is usually benign; however, a WARN will be triggered if one of the child kobjects has a named attribute group: sysfs group 'modes' not found for kobject 'crypto' WARNING: CPU: 0 PID: 1 at fs/sysfs/group.c:278 sysfs_remove_group+0x72/0x80 ... Call Trace: sysfs_remove_groups+0x29/0x40 fs/sysfs/group.c:312 __kobject_del+0x20/0x80 lib/kobject.c:611 kobject_cleanup+0xa4/0x140 lib/kobject.c:696 kobject_release lib/kobject.c:736 [inline] kref_put include/linux/kref.h:65 [inline] kobject_put+0x53/0x70 lib/kobject.c:753 blk_crypto_sysfs_unregister+0x10/0x20 block/blk-crypto-sysfs.c:159 blk_unregister_queue+0xb0/0x110 block/blk-sysfs.c:962 del_gendisk+0x117/0x250 block/genhd.c:610 Fix this by moving the kobject_del() and the corresponding kobject_uevent() to the correct place.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 4.19.238, 5.10.110, 5.15.33, 5.16.19, 5.17.2, 5.4.189
- CVEs
- CVE-2022-49259
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 23:16 UTC · Revision 1
Source evidence
block: don't delete queue kobject before its children
core-osv · Original sourcePublished 26 Feb 2025, 01:56 UTC
In the Linux kernel, the following vulnerability has been resolved: block: don't delete queue kobject before its children kobjects aren't supposed to be deleted before their child kobjects are deleted. Apparently this is usually benign; however, a WARN will be triggered if one of the child kobjects has a named attribute group: sysfs group 'modes' not found for kobject 'crypto' WARNING: CPU: 0 PID: 1 at fs/sysfs/group.c:278 sysfs_remove_group+0x72/0x80 ... Call Trace: sysfs_remove_groups+0x29/0x40 fs/sysfs/group.c:312 __kobject_del+0x20/0x80 lib/kobject.c:611 kobject_cleanup+0xa4/0x140 lib/kobject.c:696 kobject_release lib/kobject.c:736 [inline] kref_put include/linux/kref.h:65 [inline] kobject_put+0x53/0x70 lib/kobject.c:753 blk_crypto_sysfs_unregister+0x10/0x20 block/blk-crypto-sysfs.c:159 blk_unregister_queue+0xb0/0x110 block/blk-sysfs.c:962 del_gendisk+0x117/0x250 block/genhd.c:610 Fix this by moving the kobject_del() and the corresponding kobject_uevent() to the correct place.
osv:CVE-2022-49259
Kernel
Fixed versions: 4.19.238, 5.4.189, 5.10.110, 5.15.33, 5.16.19, 5.17.2
Complete source record
{
"id": "04e8bd7aae18aaf447e68650a3505b529425144c620f1ab009e7501f0d069d41",
"url": "https://osv.dev/vulnerability/CVE-2022-49259",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "block: don't delete queue kobject before its children",
"summary": "In the Linux kernel, the following vulnerability has been resolved: block: don't delete queue kobject before its children kobjects aren't supposed to be deleted before their child kobjects are deleted. Apparently this is usually benign; however, a WARN will be triggered if one of the child kobjects has a named attribute group: sysfs group 'modes' not found for kobject 'crypto' WARNING: CPU: 0 PID: 1 at fs/sysfs/group.c:278 sysfs_remove_group+0x72/0x80 ... Call Trace: sysfs_remove_groups+0x29/0x40 fs/sysfs/group.c:312 __kobject_del+0x20/0x80 lib/kobject.c:611 kobject_cleanup+0xa4/0x140 lib/kobject.c:696 kobject_release lib/kobject.c:736 [inline] kref_put include/linux/kref.h:65 [inline] kobject_put+0x53/0x70 lib/kobject.c:753 blk_crypto_sysfs_unregister+0x10/0x20 block/blk-crypto-sysfs.c:159 blk_unregister_queue+0xb0/0x110 block/blk-sysfs.c:962 del_gendisk+0x117/0x250 block/genhd.c:610 Fix this by moving the kobject_del() and the corresponding kobject_uevent() to the correct place.",
"evidence": "osv:CVE-2022-49259",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "4.19.238",
"evidence": "/affected/1/ranges"
},
{
"value": "5.4.189",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.110",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.33",
"evidence": "/affected/1/ranges"
},
{
"value": "5.16.19",
"evidence": "/affected/1/ranges"
},
{
"value": "5.17.2",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2022-49259",
"aliases": [
"CVE-2022-49259"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "2c2086afc2b8b974fac32cb028e73dc27bfae442"
},
{
"fixed": "b2001eb10f59363da930cdd6e086a2861986fa18"
},
{
"fixed": "84fe3ca6e7910beb47ec13509d484f84fa2a41ad"
},
{
"fixed": "0b5924a14d64487ebd51127b0358d06066ef5384"
},
{
"fixed": "efaa0e969261e97c1fdd8e0338e5dd3ba5b9219c"
},
{
"fixed": "cf0cb8686e55d9c022944bc6ba9e19e832889e83"
},
{
"fixed": "3d7e32c8da45957326f56937e0471c686d1a7711"
},
{
"fixed": "0f69288253e9fc7c495047720e523b9f1aba5712"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49259.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.16.0"
},
{
"fixed": "4.19.238"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.20.0"
},
{
"fixed": "5.4.189"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.110"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.33"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "5.16.19"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.17.0"
},
{
"fixed": "5.17.2"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49259.json"
}
}
],
"modified": "2026-10-28T02:30:24.558360067Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/0b5924a14d64487ebd51127b0358d06066ef5384",
"https://git.kernel.org/stable/c/0f69288253e9fc7c495047720e523b9f1aba5712",
"https://git.kernel.org/stable/c/3d7e32c8da45957326f56937e0471c686d1a7711",
"https://git.kernel.org/stable/c/84fe3ca6e7910beb47ec13509d484f84fa2a41ad",
"https://git.kernel.org/stable/c/b2001eb10f59363da930cdd6e086a2861986fa18",
"https://git.kernel.org/stable/c/cf0cb8686e55d9c022944bc6ba9e19e832889e83",
"https://git.kernel.org/stable/c/efaa0e969261e97c1fdd8e0338e5dd3ba5b9219c",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49259.json",
"https://nvd.nist.gov/vuln/detail/CVE-2022-49259",
"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/2022/49xxx/CVE-2022-49259.json"
}
},
"related_cves": [
{
"value": "CVE-2022-49259",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 490815,
"published_at": "2025-02-26T01:56:12.046+00:00"
}