s390/ap: use generic driver_override infrastructure
In the Linux kernel, the following vulnerability has been resolved: s390/ap: use generic driver_override infrastructure When the AP masks are updated via apmask_store() or aqmask_store(), ap_bus_revise_bindings() is called after ap_attr_mutex has been released. This calls __ap_revise_reserved(), which accesses the driver_override field without holding any lock, racing against a concurrent driver_override_store() that may free the old string, resulting in a potential UAF. Fix this by using the driver-core driver_override infrastructure, which protects all accesses with an internal spinlock. Note that unlike most other buses, the AP bus does not check driver_override in its match() callback; the override is checked in ap_device_probe() and __ap_revise_reserved() instead. Also note that we do not enable the driver_override feature of struct bus_type, as AP - in contrast to most other buses - passes "" to sysfs_emit() when the driver_override pointer is NULL. Thus, printing "\n" instead of "(null)\n". Additionally, AP has a custom counter that is modified in the corresponding custom driver_override_store().
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 7.0.10
- CVEs
- CVE-2026-53116
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 07:00 UTC · Revision 1
Source evidence
s390/ap: use generic driver_override infrastructure
core-osv · Original sourcePublished 24 Jun 2026, 16:30 UTC
In the Linux kernel, the following vulnerability has been resolved: s390/ap: use generic driver_override infrastructure When the AP masks are updated via apmask_store() or aqmask_store(), ap_bus_revise_bindings() is called after ap_attr_mutex has been released. This calls __ap_revise_reserved(), which accesses the driver_override field without holding any lock, racing against a concurrent driver_override_store() that may free the old string, resulting in a potential UAF. Fix this by using the driver-core driver_override infrastructure, which protects all accesses with an internal spinlock. Note that unlike most other buses, the AP bus does not check driver_override in its match() callback; the override is checked in ap_device_probe() and __ap_revise_reserved() instead. Also note that we do not enable the driver_override feature of struct bus_type, as AP - in contrast to most other buses - passes "" to sysfs_emit() when the driver_override pointer is NULL. Thus, printing "\n" instead of "(null)\n". Additionally, AP has a custom counter that is modified in the corresponding custom driver_override_store().
osv:CVE-2026-53116
Kernel
Fixed versions: 7.0.10
Complete source record
{
"id": "ead6af8f68d8f3caa2cd1188b2f5c8774b199eb7f436688af91905411c81a171",
"url": "https://osv.dev/vulnerability/CVE-2026-53116",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "s390/ap: use generic driver_override infrastructure",
"summary": "In the Linux kernel, the following vulnerability has been resolved: s390/ap: use generic driver_override infrastructure When the AP masks are updated via apmask_store() or aqmask_store(), ap_bus_revise_bindings() is called after ap_attr_mutex has been released. This calls __ap_revise_reserved(), which accesses the driver_override field without holding any lock, racing against a concurrent driver_override_store() that may free the old string, resulting in a potential UAF. Fix this by using the driver-core driver_override infrastructure, which protects all accesses with an internal spinlock. Note that unlike most other buses, the AP bus does not check driver_override in its match() callback; the override is checked in ap_device_probe() and __ap_revise_reserved() instead. Also note that we do not enable the driver_override feature of struct bus_type, as AP - in contrast to most other buses - passes \"\" to sysfs_emit() when the driver_override pointer is NULL. Thus, printing \"\\n\" instead of \"(null)\\n\". Additionally, AP has a custom counter that is modified in the corresponding custom driver_override_store().",
"evidence": "osv:CVE-2026-53116",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "7.0.10",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-53116",
"aliases": [
"CVE-2026-53116"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "d38a87d7c0643db61e7a3bfc3ebeea2dc2568f7e"
},
{
"fixed": "8f2eca0570438b94602da1297353eb7b10dcb6cb"
},
{
"fixed": "81d6f7c3a70b10ff757ee8b5f8114a190871cf1e"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53116.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.0.10"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53116.json"
}
}
],
"modified": "2026-10-28T02:30:26.862245549Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/81d6f7c3a70b10ff757ee8b5f8114a190871cf1e",
"https://git.kernel.org/stable/c/8f2eca0570438b94602da1297353eb7b10dcb6cb",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53116.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-53116",
"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/2026/53xxx/CVE-2026-53116.json"
}
},
"related_cves": [
{
"value": "CVE-2026-53116",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 493199,
"published_at": "2026-06-24T16:30:47.982+00:00"
}