tracing/eprobes: Have event probes be consistent with kprobes and uprobes
In the Linux kernel, the following vulnerability has been resolved: tracing/eprobes: Have event probes be consistent with kprobes and uprobes Currently, if a symbol "@" is attempted to be used with an event probe (eprobes), it will cause a NULL pointer dereference crash. Both kprobes and uprobes can reference data other than the main registers. Such as immediate address, symbols and the current task name. Have eprobes do the same thing. For "comm", if "comm" is used and the event being attached to does not have the "comm" field, then make it the "$comm" that kprobes has. This is consistent to the way histograms and filters work.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.15.63, 5.19.4
- CVEs
- CVE-2022-50075
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 10:40 UTC · Revision 1
Source evidence
tracing/eprobes: Have event probes be consistent with kprobes and uprobes
core-osv · Original sourcePublished 18 Jun 2025, 11:02 UTC
In the Linux kernel, the following vulnerability has been resolved: tracing/eprobes: Have event probes be consistent with kprobes and uprobes Currently, if a symbol "@" is attempted to be used with an event probe (eprobes), it will cause a NULL pointer dereference crash. Both kprobes and uprobes can reference data other than the main registers. Such as immediate address, symbols and the current task name. Have eprobes do the same thing. For "comm", if "comm" is used and the event being attached to does not have the "comm" field, then make it the "$comm" that kprobes has. This is consistent to the way histograms and filters work.
osv:CVE-2022-50075
Kernel
Fixed versions: 5.15.63, 5.19.4
Complete source record
{
"id": "17f9650c0c2c1c6c8be0ffef79c93153eac3336a54215c8787eeaf8cd54fe029",
"url": "https://osv.dev/vulnerability/CVE-2022-50075",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "tracing/eprobes: Have event probes be consistent with kprobes and uprobes",
"summary": "In the Linux kernel, the following vulnerability has been resolved: tracing/eprobes: Have event probes be consistent with kprobes and uprobes Currently, if a symbol \"@\" is attempted to be used with an event probe (eprobes), it will cause a NULL pointer dereference crash. Both kprobes and uprobes can reference data other than the main registers. Such as immediate address, symbols and the current task name. Have eprobes do the same thing. For \"comm\", if \"comm\" is used and the event being attached to does not have the \"comm\" field, then make it the \"$comm\" that kprobes has. This is consistent to the way histograms and filters work.",
"evidence": "osv:CVE-2022-50075",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.15.63",
"evidence": "/affected/1/ranges"
},
{
"value": "5.19.4",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2022-50075",
"aliases": [
"CVE-2022-50075"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "7491e2c442781a1860181adb5ab472a52075f393"
},
{
"fixed": "b489aca082a23033a3d8355cfb0032f0e2523440"
},
{
"fixed": "47cc883f21fa3bcf24891b4b455f4cd461ce2d6e"
},
{
"fixed": "6a832ec3d680b3a4f4fad5752672827d71bae501"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-50075.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.15.0"
},
{
"fixed": "5.15.63"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "5.19.4"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-50075.json"
}
}
],
"modified": "2026-10-28T02:30:27.973153121Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/47cc883f21fa3bcf24891b4b455f4cd461ce2d6e",
"https://git.kernel.org/stable/c/6a832ec3d680b3a4f4fad5752672827d71bae501",
"https://git.kernel.org/stable/c/b489aca082a23033a3d8355cfb0032f0e2523440",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50075.json",
"https://nvd.nist.gov/vuln/detail/CVE-2022-50075",
"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/50xxx/CVE-2022-50075.json"
}
},
"related_cves": [
{
"value": "CVE-2022-50075",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 494616,
"published_at": "2025-06-18T11:02:18.851+00:00"
}