CVE-2022-48647
Vulnerability from cvelistv5
Published
2024-04-28 13:00
Modified
2024-11-04 12:13
Severity ?
EPSS score ?
Summary
sfc: fix TX channel offset when using legacy interrupts
References
Impacted products
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2022-48647",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-06-17T19:07:40.953433Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2024-06-17T19:07:53.011Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
},
{
"providerMetadata": {
"dateUpdated": "2024-08-03T15:17:55.568Z",
"orgId": "af854a3a-2127-422b-91ae-364da2661108",
"shortName": "CVE"
},
"references": [
{
"tags": [
"x_transferred"
],
"url": "https://git.kernel.org/stable/c/b4afd3878f961d3517f27b3213730fceef77945c"
},
{
"tags": [
"x_transferred"
],
"url": "https://git.kernel.org/stable/c/360910b88d1466a90644a4e0533803b594344a2b"
},
{
"tags": [
"x_transferred"
],
"url": "https://git.kernel.org/stable/c/5f623a77cfc2d501d72bcb4f9ee71721e6c766ff"
},
{
"tags": [
"x_transferred"
],
"url": "https://git.kernel.org/stable/c/f232af4295653afa4ade3230462b3be15ad16419"
}
],
"title": "CVE Program Container"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/net/ethernet/sfc/efx_channels.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "b4afd3878f96",
"status": "affected",
"version": "bf2af9b24313",
"versionType": "git"
},
{
"lessThan": "360910b88d14",
"status": "affected",
"version": "06cb7e134f8f",
"versionType": "git"
},
{
"lessThan": "5f623a77cfc2",
"status": "affected",
"version": "c308dfd1b43e",
"versionType": "git"
},
{
"lessThan": "f232af429565",
"status": "affected",
"version": "c308dfd1b43e",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/net/ethernet/sfc/efx_channels.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.19"
},
{
"lessThan": "5.19",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.10.*",
"status": "unaffected",
"version": "5.10.146",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.71",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.19.*",
"status": "unaffected",
"version": "5.19.12",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.0",
"versionType": "original_commit_for_fix"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsfc: fix TX channel offset when using legacy interrupts\n\nIn legacy interrupt mode the tx_channel_offset was hardcoded to 1, but\nthat\u0027s not correct if efx_sepparate_tx_channels is false. In that case,\nthe offset is 0 because the tx queues are in the single existing channel\nat index 0, together with the rx queue.\n\nWithout this fix, as soon as you try to send any traffic, it tries to\nget the tx queues from an uninitialized channel getting these errors:\n WARNING: CPU: 1 PID: 0 at drivers/net/ethernet/sfc/tx.c:540 efx_hard_start_xmit+0x12e/0x170 [sfc]\n [...]\n RIP: 0010:efx_hard_start_xmit+0x12e/0x170 [sfc]\n [...]\n Call Trace:\n \u003cIRQ\u003e\n dev_hard_start_xmit+0xd7/0x230\n sch_direct_xmit+0x9f/0x360\n __dev_queue_xmit+0x890/0xa40\n [...]\n BUG: unable to handle kernel NULL pointer dereference at 0000000000000020\n [...]\n RIP: 0010:efx_hard_start_xmit+0x153/0x170 [sfc]\n [...]\n Call Trace:\n \u003cIRQ\u003e\n dev_hard_start_xmit+0xd7/0x230\n sch_direct_xmit+0x9f/0x360\n __dev_queue_xmit+0x890/0xa40\n [...]"
}
],
"providerMetadata": {
"dateUpdated": "2024-11-04T12:13:55.262Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/b4afd3878f961d3517f27b3213730fceef77945c"
},
{
"url": "https://git.kernel.org/stable/c/360910b88d1466a90644a4e0533803b594344a2b"
},
{
"url": "https://git.kernel.org/stable/c/5f623a77cfc2d501d72bcb4f9ee71721e6c766ff"
},
{
"url": "https://git.kernel.org/stable/c/f232af4295653afa4ade3230462b3be15ad16419"
}
],
"title": "sfc: fix TX channel offset when using legacy interrupts",
"x_generator": {
"engine": "bippy-9e1c9544281a"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2022-48647",
"datePublished": "2024-04-28T13:00:19.674Z",
"dateReserved": "2024-02-25T13:44:28.316Z",
"dateUpdated": "2024-11-04T12:13:55.262Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.1",
"meta": {
"nvd": "{\"cve\":{\"id\":\"CVE-2022-48647\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-04-28T13:15:07.237\",\"lastModified\":\"2024-04-29T12:42:03.667\",\"vulnStatus\":\"Awaiting Analysis\",\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nsfc: fix TX channel offset when using legacy interrupts\\n\\nIn legacy interrupt mode the tx_channel_offset was hardcoded to 1, but\\nthat\u0027s not correct if efx_sepparate_tx_channels is false. In that case,\\nthe offset is 0 because the tx queues are in the single existing channel\\nat index 0, together with the rx queue.\\n\\nWithout this fix, as soon as you try to send any traffic, it tries to\\nget the tx queues from an uninitialized channel getting these errors:\\n WARNING: CPU: 1 PID: 0 at drivers/net/ethernet/sfc/tx.c:540 efx_hard_start_xmit+0x12e/0x170 [sfc]\\n [...]\\n RIP: 0010:efx_hard_start_xmit+0x12e/0x170 [sfc]\\n [...]\\n Call Trace:\\n \u003cIRQ\u003e\\n dev_hard_start_xmit+0xd7/0x230\\n sch_direct_xmit+0x9f/0x360\\n __dev_queue_xmit+0x890/0xa40\\n [...]\\n BUG: unable to handle kernel NULL pointer dereference at 0000000000000020\\n [...]\\n RIP: 0010:efx_hard_start_xmit+0x153/0x170 [sfc]\\n [...]\\n Call Trace:\\n \u003cIRQ\u003e\\n dev_hard_start_xmit+0xd7/0x230\\n sch_direct_xmit+0x9f/0x360\\n __dev_queue_xmit+0x890/0xa40\\n [...]\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: sfc: corrige el desplazamiento del canal TX cuando se usan interrupciones heredadas En el modo de interrupci\u00f3n heredado, tx_channel_offset estaba codificado en 1, pero eso no es correcto si efx_sepparate_tx_channels es falso. En ese caso, el desplazamiento es 0 porque las colas de transmisi\u00f3n est\u00e1n en el \u00fanico canal existente en el \u00edndice 0, junto con la cola de recepci\u00f3n. Sin esta soluci\u00f3n, tan pronto como intenta enviar tr\u00e1fico, intenta obtener las colas de transmisi\u00f3n de un canal no inicializado y obtiene estos errores: ADVERTENCIA: CPU: 1 PID: 0 en drivers/net/ethernet/sfc/tx.c: 540 efx_hard_start_xmit+0x12e/0x170 [sfc] [...] RIP: 0010:efx_hard_start_xmit+0x12e/0x170 [sfc] [...] Seguimiento de llamadas: dev_hard_start_xmit+0xd7/0x230 sch_direct_xmit+0x9f/0x360 +0x890 /0xa40 [...] ERROR: no se puede manejar la desreferencia del puntero NULL del kernel en 0000000000000020 [...] RIP: 0010:efx_hard_start_xmit+0x153/0x170 [sfc] [...] Seguimiento de llamadas: dev_hard_start_xmit+0xd7/ 0x230 sch_direct_xmit+0x9f/0x360 __dev_queue_xmit+0x890/0xa40 [...]\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/360910b88d1466a90644a4e0533803b594344a2b\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/5f623a77cfc2d501d72bcb4f9ee71721e6c766ff\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/b4afd3878f961d3517f27b3213730fceef77945c\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/f232af4295653afa4ade3230462b3be15ad16419\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.