CVE-2026-46264 (GCVE-0-2026-46264)
Vulnerability from cvelistv5 – Published: 2026-06-03 15:50 – Updated: 2026-06-03 15:50
VLAI
Title
drm/xe/pf: Fix sysfs initialization
Summary
In the Linux kernel, the following vulnerability has been resolved:
drm/xe/pf: Fix sysfs initialization
In case of devm_add_action_or_reset() failure the provided cleanup
action will be run immediately on the not yet initialized kobject.
This may lead to errors like:
[ ] kobject: '(null)' (ff110001393608e0): is not initialized, yet kobject_put() is being called.
[ ] WARNING: lib/kobject.c:734 at kobject_put+0xd9/0x250, CPU#0: kworker/0:0/9
[ ] RIP: 0010:kobject_put+0xdf/0x250
[ ] Call Trace:
[ ] xe_sriov_pf_sysfs_init+0x21/0x100 [xe]
[ ] xe_sriov_pf_init_late+0x87/0x2b0 [xe]
[ ] xe_sriov_init_late+0x5f/0x2c0 [xe]
[ ] xe_device_probe+0x5f2/0xc20 [xe]
[ ] xe_pci_probe+0x396/0x610 [xe]
[ ] local_pci_probe+0x47/0xb0
[ ] refcount_t: underflow; use-after-free.
[ ] WARNING: lib/refcount.c:28 at refcount_warn_saturate+0x68/0xb0, CPU#0: kworker/0:0/9
[ ] RIP: 0010:refcount_warn_saturate+0x68/0xb0
[ ] Call Trace:
[ ] kobject_put+0x174/0x250
[ ] xe_sriov_pf_sysfs_init+0x21/0x100 [xe]
[ ] xe_sriov_pf_init_late+0x87/0x2b0 [xe]
[ ] xe_sriov_init_late+0x5f/0x2c0 [xe]
[ ] xe_device_probe+0x5f2/0xc20 [xe]
[ ] xe_pci_probe+0x396/0x610 [xe]
[ ] local_pci_probe+0x47/0xb0
Fix that by calling kobject_init() and kobject_add() separately
and register cleanup action after the kobject is initialized.
Also make this cleanup registration a part of the create helper to
fix another mistake, as in the loop we were wrongly passing parent
kobject while registering cleanup action, and this resulted in some
undetected leaks.
(cherry picked from commit 98b16727f07e26a5d4de84d88805ce7ffcfdd324)
Severity
No CVSS data available.
Assigner
References
Impacted products
2 products
| Vendor | Product | Version | |
|---|---|---|---|
| Linux | Linux |
Affected:
5c170a4d9c530e872f2f788d95258fbaa39b4415 , < 6ae479b1919ee9bd0560fc7af649932dd420d010
(git)
Affected: 5c170a4d9c530e872f2f788d95258fbaa39b4415 , < bf7172cd25ed182f30af2cbb9f80c730dc717d8e (git) |
|
| Linux | Linux |
Affected:
6.19
Unaffected: 0 , < 6.19 (semver) Unaffected: 6.19.4 , ≤ 6.19.* (semver) Unaffected: 7.0 , ≤ * (original_commit_for_fix) |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/xe/xe_sriov_pf_sysfs.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "6ae479b1919ee9bd0560fc7af649932dd420d010",
"status": "affected",
"version": "5c170a4d9c530e872f2f788d95258fbaa39b4415",
"versionType": "git"
},
{
"lessThan": "bf7172cd25ed182f30af2cbb9f80c730dc717d8e",
"status": "affected",
"version": "5c170a4d9c530e872f2f788d95258fbaa39b4415",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/xe/xe_sriov_pf_sysfs.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.19"
},
{
"lessThan": "6.19",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.19.*",
"status": "unaffected",
"version": "6.19.4",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.0",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.19.4",
"versionStartIncluding": "6.19",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.0",
"versionStartIncluding": "6.19",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/xe/pf: Fix sysfs initialization\n\nIn case of devm_add_action_or_reset() failure the provided cleanup\naction will be run immediately on the not yet initialized kobject.\nThis may lead to errors like:\n\n [ ] kobject: \u0027(null)\u0027 (ff110001393608e0): is not initialized, yet kobject_put() is being called.\n [ ] WARNING: lib/kobject.c:734 at kobject_put+0xd9/0x250, CPU#0: kworker/0:0/9\n [ ] RIP: 0010:kobject_put+0xdf/0x250\n [ ] Call Trace:\n [ ] xe_sriov_pf_sysfs_init+0x21/0x100 [xe]\n [ ] xe_sriov_pf_init_late+0x87/0x2b0 [xe]\n [ ] xe_sriov_init_late+0x5f/0x2c0 [xe]\n [ ] xe_device_probe+0x5f2/0xc20 [xe]\n [ ] xe_pci_probe+0x396/0x610 [xe]\n [ ] local_pci_probe+0x47/0xb0\n\n [ ] refcount_t: underflow; use-after-free.\n [ ] WARNING: lib/refcount.c:28 at refcount_warn_saturate+0x68/0xb0, CPU#0: kworker/0:0/9\n [ ] RIP: 0010:refcount_warn_saturate+0x68/0xb0\n [ ] Call Trace:\n [ ] kobject_put+0x174/0x250\n [ ] xe_sriov_pf_sysfs_init+0x21/0x100 [xe]\n [ ] xe_sriov_pf_init_late+0x87/0x2b0 [xe]\n [ ] xe_sriov_init_late+0x5f/0x2c0 [xe]\n [ ] xe_device_probe+0x5f2/0xc20 [xe]\n [ ] xe_pci_probe+0x396/0x610 [xe]\n [ ] local_pci_probe+0x47/0xb0\n\nFix that by calling kobject_init() and kobject_add() separately\nand register cleanup action after the kobject is initialized.\n\nAlso make this cleanup registration a part of the create helper to\nfix another mistake, as in the loop we were wrongly passing parent\nkobject while registering cleanup action, and this resulted in some\nundetected leaks.\n\n(cherry picked from commit 98b16727f07e26a5d4de84d88805ce7ffcfdd324)"
}
],
"providerMetadata": {
"dateUpdated": "2026-06-03T15:50:04.620Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/6ae479b1919ee9bd0560fc7af649932dd420d010"
},
{
"url": "https://git.kernel.org/stable/c/bf7172cd25ed182f30af2cbb9f80c730dc717d8e"
}
],
"title": "drm/xe/pf: Fix sysfs initialization",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-46264",
"datePublished": "2026-06-03T15:50:04.620Z",
"dateReserved": "2026-05-13T15:03:33.108Z",
"dateUpdated": "2026-06-03T15:50:04.620Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": "{\"cve\":{\"id\":\"CVE-2026-46264\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-06-03T18:16:27.893\",\"lastModified\":\"2026-06-03T18:16:27.893\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\ndrm/xe/pf: Fix sysfs initialization\\n\\nIn case of devm_add_action_or_reset() failure the provided cleanup\\naction will be run immediately on the not yet initialized kobject.\\nThis may lead to errors like:\\n\\n [ ] kobject: \u0027(null)\u0027 (ff110001393608e0): is not initialized, yet kobject_put() is being called.\\n [ ] WARNING: lib/kobject.c:734 at kobject_put+0xd9/0x250, CPU#0: kworker/0:0/9\\n [ ] RIP: 0010:kobject_put+0xdf/0x250\\n [ ] Call Trace:\\n [ ] xe_sriov_pf_sysfs_init+0x21/0x100 [xe]\\n [ ] xe_sriov_pf_init_late+0x87/0x2b0 [xe]\\n [ ] xe_sriov_init_late+0x5f/0x2c0 [xe]\\n [ ] xe_device_probe+0x5f2/0xc20 [xe]\\n [ ] xe_pci_probe+0x396/0x610 [xe]\\n [ ] local_pci_probe+0x47/0xb0\\n\\n [ ] refcount_t: underflow; use-after-free.\\n [ ] WARNING: lib/refcount.c:28 at refcount_warn_saturate+0x68/0xb0, CPU#0: kworker/0:0/9\\n [ ] RIP: 0010:refcount_warn_saturate+0x68/0xb0\\n [ ] Call Trace:\\n [ ] kobject_put+0x174/0x250\\n [ ] xe_sriov_pf_sysfs_init+0x21/0x100 [xe]\\n [ ] xe_sriov_pf_init_late+0x87/0x2b0 [xe]\\n [ ] xe_sriov_init_late+0x5f/0x2c0 [xe]\\n [ ] xe_device_probe+0x5f2/0xc20 [xe]\\n [ ] xe_pci_probe+0x396/0x610 [xe]\\n [ ] local_pci_probe+0x47/0xb0\\n\\nFix that by calling kobject_init() and kobject_add() separately\\nand register cleanup action after the kobject is initialized.\\n\\nAlso make this cleanup registration a part of the create helper to\\nfix another mistake, as in the loop we were wrongly passing parent\\nkobject while registering cleanup action, and this resulted in some\\nundetected leaks.\\n\\n(cherry picked from commit 98b16727f07e26a5d4de84d88805ce7ffcfdd324)\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/6ae479b1919ee9bd0560fc7af649932dd420d010\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/bf7172cd25ed182f30af2cbb9f80c730dc717d8e\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…