GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

CVE-2022-48696 (GCVE-0-2022-48696)

Vulnerability from cvelistv5 – Published: 2024-05-03 15:09 – Updated: 2026-08-05 08:51
VLAI
Title
regmap: spi: Reserve space for register address/padding
Summary
In the Linux kernel, the following vulnerability has been resolved: regmap: spi: Reserve space for register address/padding Currently the max_raw_read and max_raw_write limits in regmap_spi struct do not take into account the additional size of the transmitted register address and padding. This may result in exceeding the maximum permitted SPI message size, which could cause undefined behaviour, e.g. data corruption. Fix regmap_get_spi_bus() to properly adjust the above mentioned limits by reserving space for the register address/padding as set in the regmap configuration.
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2024-05-03 19:17 UTC
CWE
  • CWE-120 - Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: f231ff38b7b23197013b437128d196710fe282da , < 15ff1f17847c19174b260bd7dd0de33edcebd45e (git)
Affected: f231ff38b7b23197013b437128d196710fe282da , < f5723cfc01932c7a8d5c78dbf7e067e537c91439 (git)
guessed Create a notification for this product.
Linux Linux Affected: 5.16
Unaffected: 0 , < 5.16 (semver)
Unaffected: 5.19.9 , ≤ 5.19.* (semver)
Unaffected: 6.0 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "cvssV3_1": {
              "attackComplexity": "LOW",
              "attackVector": "LOCAL",
              "availabilityImpact": "NONE",
              "baseScore": 5.5,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "NONE",
              "integrityImpact": "HIGH",
              "privilegesRequired": "LOW",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
              "version": "3.1"
            }
          },
          {
            "other": {
              "content": {
                "id": "CVE-2022-48696",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-05-03T19:17:13.192981Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "problemTypes": [
          {
            "descriptions": [
              {
                "cweId": "CWE-120",
                "description": "CWE-120 Buffer Copy without Checking Size of Input (\u0027Classic Buffer Overflow\u0027)",
                "lang": "en",
                "type": "CWE"
              }
            ]
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-11-20T14:43:46.697Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      },
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-03T15:17:55.746Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/15ff1f17847c19174b260bd7dd0de33edcebd45e"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/f5723cfc01932c7a8d5c78dbf7e067e537c91439"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/base/regmap/regmap-spi.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "15ff1f17847c19174b260bd7dd0de33edcebd45e",
              "status": "affected",
              "version": "f231ff38b7b23197013b437128d196710fe282da",
              "versionType": "git"
            },
            {
              "lessThan": "f5723cfc01932c7a8d5c78dbf7e067e537c91439",
              "status": "affected",
              "version": "f231ff38b7b23197013b437128d196710fe282da",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/base/regmap/regmap-spi.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.16"
            },
            {
              "lessThan": "5.16",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.19.*",
              "status": "unaffected",
              "version": "5.19.9",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.0",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.19.9",
                  "versionStartIncluding": "5.16",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.0",
                  "versionStartIncluding": "5.16",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nregmap: spi: Reserve space for register address/padding\n\nCurrently the max_raw_read and max_raw_write limits in regmap_spi struct\ndo not take into account the additional size of the transmitted register\naddress and padding.  This may result in exceeding the maximum permitted\nSPI message size, which could cause undefined behaviour, e.g. data\ncorruption.\n\nFix regmap_get_spi_bus() to properly adjust the above mentioned limits\nby reserving space for the register address/padding as set in the regmap\nconfiguration."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.1,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The flaw is in kernel SPI regmap sizing used by local device drivers (codecs, sensors, MFDs) when performing raw/bulk register I/O; it is not reachable via network protocols or adjacent-link frames, and does not require physical SPI pin access.\nAC:L - On SPI controllers that publish a finite max_message_size, oversized chunking is deterministic arithmetic (max_raw equals max_transfer without reserving reg/pad bytes), so a large regmap_raw_read/write reliably produces an over-limit message with no race or attacker-uncontrollable timing.\nPR:L - Large SPI regmap transfers are reachable from unprivileged local contexts that exercise device interfaces which load firmware or perform bulk I/O (e.g., ALSA/HDA paths that drive Cirrus cs_dsp regmap_raw_write_async, IIO/sysfs device access), without needing init-namespace root or capabilities.\nUI:N - The attacker triggers the oversized SPI message solely by driving their own device I/O or firmware-load path; no separate victim action such as mounting a filesystem or opening a crafted file is required.\nS:U - Impact stays within the host kernel and attached SPI device/controller under the same OS security authority; there is no VM escape, IOMMU bypass, or other cross-boundary effect.\nC:N - The defect causes oversized SPI messages and potential write-side FIFO/MMIO corruption; receive buffers remain caller-sized, and there is no OOB read, UAF, or other kernel information-disclosure primitive.\nI:H - Exceeding max SPI message size yields undefined behavior and data corruption as stated in the fix, and on controllers without a secondary length check (e.g., amd_spi FIFO MMIO writes) constitutes an out-of-bounds write past the hardware FIFO into adjacent controller state\u2014treated as High per OOB-write guidance.\nA:H - Oversized transfers can fail, time out, or leave SPI controller/device state corrupted so subsequent I/O hangs or faults; when choosing between no availability impact and sustained device/controller denial of service, High is the more severe defensible rating."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T08:51:49.444Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/15ff1f17847c19174b260bd7dd0de33edcebd45e"
        },
        {
          "url": "https://git.kernel.org/stable/c/f5723cfc01932c7a8d5c78dbf7e067e537c91439"
        }
      ],
      "title": "regmap: spi: Reserve space for register address/padding",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2022-48696",
    "datePublished": "2024-05-03T15:09:48.280Z",
    "dateReserved": "2024-05-03T14:55:07.145Z",
    "dateUpdated": "2026-08-05T08:51:49.444Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2022-48696",
      "date": "2026-09-14",
      "epss": "0.00197",
      "percentile": "0.096"
    },
    "fkie_nvd": {
      "descriptions": "[{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nregmap: spi: Reserve space for register address/padding\\n\\nCurrently the max_raw_read and max_raw_write limits in regmap_spi struct\\ndo not take into account the additional size of the transmitted register\\naddress and padding.  This may result in exceeding the maximum permitted\\nSPI message size, which could cause undefined behaviour, e.g. data\\ncorruption.\\n\\nFix regmap_get_spi_bus() to properly adjust the above mentioned limits\\nby reserving space for the register address/padding as set in the regmap\\nconfiguration.\"}, {\"lang\": \"es\", \"value\": \"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: regmap: spi: reserva de espacio para direcci\\u00f3n/relleno de registro Actualmente, los l\\u00edmites max_raw_read y max_raw_write en la estructura regmap_spi no tienen en cuenta el tama\\u00f1o adicional de la direcci\\u00f3n de registro transmitida y el relleno. Esto puede dar como resultado que se exceda el tama\\u00f1o de mensaje SPI m\\u00e1ximo permitido, lo que podr\\u00eda causar un comportamiento indefinido, por ejemplo, corrupci\\u00f3n de datos. Corrija regmap_get_spi_bus() para ajustar adecuadamente los l\\u00edmites mencionados anteriormente reservando espacio para la direcci\\u00f3n/relleno del registro como se establece en la configuraci\\u00f3n de regmap.\"}]",
      "id": "CVE-2022-48696",
      "lastModified": "2024-11-21T07:33:48.377",
      "metrics": "{\"cvssMetricV31\": [{\"source\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"type\": \"Secondary\", \"cvssData\": {\"version\": \"3.1\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N\", \"baseScore\": 5.5, \"baseSeverity\": \"MEDIUM\", \"attackVector\": \"LOCAL\", \"attackComplexity\": \"LOW\", \"privilegesRequired\": \"LOW\", \"userInteraction\": \"NONE\", \"scope\": \"UNCHANGED\", \"confidentialityImpact\": \"NONE\", \"integrityImpact\": \"HIGH\", \"availabilityImpact\": \"NONE\"}, \"exploitabilityScore\": 1.8, \"impactScore\": 3.6}]}",
      "published": "2024-05-03T16:15:08.290",
      "references": "[{\"url\": \"https://git.kernel.org/stable/c/15ff1f17847c19174b260bd7dd0de33edcebd45e\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/f5723cfc01932c7a8d5c78dbf7e067e537c91439\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/15ff1f17847c19174b260bd7dd0de33edcebd45e\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}, {\"url\": \"https://git.kernel.org/stable/c/f5723cfc01932c7a8d5c78dbf7e067e537c91439\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}]",
      "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "vulnStatus": "Awaiting Analysis",
      "weaknesses": "[{\"source\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"type\": \"Secondary\", \"description\": [{\"lang\": \"en\", \"value\": \"CWE-120\"}]}]"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2022-48696\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-05-03T16:15:08.290\",\"lastModified\":\"2026-08-04T10:17:16.267\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nregmap: spi: Reserve space for register address/padding\\n\\nCurrently the max_raw_read and max_raw_write limits in regmap_spi struct\\ndo not take into account the additional size of the transmitted register\\naddress and padding.  This may result in exceeding the maximum permitted\\nSPI message size, which could cause undefined behaviour, e.g. data\\ncorruption.\\n\\nFix regmap_get_spi_bus() to properly adjust the above mentioned limits\\nby reserving space for the register address/padding as set in the regmap\\nconfiguration.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: regmap: spi: reserva de espacio para direcci\u00f3n/relleno de registro Actualmente, los l\u00edmites max_raw_read y max_raw_write en la estructura regmap_spi no tienen en cuenta el tama\u00f1o adicional de la direcci\u00f3n de registro transmitida y el relleno. Esto puede dar como resultado que se exceda el tama\u00f1o de mensaje SPI m\u00e1ximo permitido, lo que podr\u00eda causar un comportamiento indefinido, por ejemplo, corrupci\u00f3n de datos. Corrija regmap_get_spi_bus() para ajustar adecuadamente los l\u00edmites mencionados anteriormente reservando espacio para la direcci\u00f3n/relleno del registro como se establece en la configuraci\u00f3n de regmap.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"drivers/base/regmap/regmap-spi.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"f231ff38b7b23197013b437128d196710fe282da\",\"lessThan\":\"15ff1f17847c19174b260bd7dd0de33edcebd45e\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"f231ff38b7b23197013b437128d196710fe282da\",\"lessThan\":\"f5723cfc01932c7a8d5c78dbf7e067e537c91439\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"drivers/base/regmap/regmap-spi.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"5.16\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"5.16\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"5.19.9\",\"lessThanOrEqual\":\"5.19.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.0\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H\",\"baseScore\":7.1,\"baseSeverity\":\"HIGH\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":5.2},{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":1.8,\"impactScore\":3.6}],\"ssvcV203\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"ssvcData\":{\"timestamp\":\"2024-05-03T19:17:13.192981Z\",\"id\":\"CVE-2022-48696\",\"options\":[{\"exploitation\":\"none\"},{\"automatable\":\"no\"},{\"technicalImpact\":\"partial\"}],\"role\":\"CISA Coordinator\",\"version\":\"2.0.3\"}}]},\"weaknesses\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-120\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.16\",\"versionEndExcluding\":\"5.19.9\",\"matchCriteriaId\":\"B4895A99-6E1B-4C76-A510-FDED00AD7D29\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.0:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"E8BD11A3-8643-49B6-BADE-5029A0117325\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.0:rc2:*:*:*:*:*:*\",\"matchCriteriaId\":\"5F0AD220-F6A9-4012-8636-155F1B841FAD\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.0:rc3:*:*:*:*:*:*\",\"matchCriteriaId\":\"A46498B3-78E1-4623-AAE1-94D29A42BE4E\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.0:rc4:*:*:*:*:*:*\",\"matchCriteriaId\":\"F8446E87-F5F6-41CA-8201-BAE0F0CA6DD9\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/15ff1f17847c19174b260bd7dd0de33edcebd45e\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/f5723cfc01932c7a8d5c78dbf7e067e537c91439\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/15ff1f17847c19174b260bd7dd0de33edcebd45e\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/f5723cfc01932c7a8d5c78dbf7e067e537c91439\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Patch\"]}]}}",
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2025-11-21T14:18:39+00:00",
      "cve": "CVE-2022-48696",
      "id": "CVE-2022-48696",
      "initial_release_date": "2022-01-01T00:00:00+00:00",
      "product_status:fixed": "615",
      "product_status:known_affected": "66",
      "product_status:known_not_affected": "54",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: regmap: spi: Reserve space for register address/padding",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2022/cve-2022-48696.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-08-31T01:38:14Z",
      "cve": "CVE-2022-48696",
      "id": "CVE-2022-48696",
      "initial_release_date": "2024-05-07T02:49:24Z",
      "product_status:known_not_affected": "385",
      "product_status:recommended": "47",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2022-48696",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2022-48696.json",
      "version": "21"
    },
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://git.kernel.org/stable/c/15ff1f17847c19174b260bd7dd0de33edcebd45e\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/f5723cfc01932c7a8d5c78dbf7e067e537c91439\", \"tags\": [\"x_transferred\"]}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2024-08-03T15:17:55.746Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 5.5, \"attackVector\": \"LOCAL\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N\", \"integrityImpact\": \"HIGH\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"NONE\", \"privilegesRequired\": \"LOW\", \"confidentialityImpact\": \"NONE\"}}, {\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2022-48696\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-05-03T19:17:13.192981Z\"}}}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-120\", \"description\": \"CWE-120 Buffer Copy without Checking Size of Input (\u0027Classic Buffer Overflow\u0027)\"}]}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-05-23T19:01:24.082Z\"}}], \"cna\": {\"title\": \"regmap: spi: Reserve space for register address/padding\", \"metrics\": [{\"cvssV3_1\": {\"version\": \"3.1\", \"baseScore\": 7.1, \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"AV:L - The flaw is in kernel SPI regmap sizing used by local device drivers (codecs, sensors, MFDs) when performing raw/bulk register I/O; it is not reachable via network protocols or adjacent-link frames, and does not require physical SPI pin access.\\nAC:L - On SPI controllers that publish a finite max_message_size, oversized chunking is deterministic arithmetic (max_raw equals max_transfer without reserving reg/pad bytes), so a large regmap_raw_read/write reliably produces an over-limit message with no race or attacker-uncontrollable timing.\\nPR:L - Large SPI regmap transfers are reachable from unprivileged local contexts that exercise device interfaces which load firmware or perform bulk I/O (e.g., ALSA/HDA paths that drive Cirrus cs_dsp regmap_raw_write_async, IIO/sysfs device access), without needing init-namespace root or capabilities.\\nUI:N - The attacker triggers the oversized SPI message solely by driving their own device I/O or firmware-load path; no separate victim action such as mounting a filesystem or opening a crafted file is required.\\nS:U - Impact stays within the host kernel and attached SPI device/controller under the same OS security authority; there is no VM escape, IOMMU bypass, or other cross-boundary effect.\\nC:N - The defect causes oversized SPI messages and potential write-side FIFO/MMIO corruption; receive buffers remain caller-sized, and there is no OOB read, UAF, or other kernel information-disclosure primitive.\\nI:H - Exceeding max SPI message size yields undefined behavior and data corruption as stated in the fix, and on controllers without a secondary length check (e.g., amd_spi FIFO MMIO writes) constitutes an out-of-bounds write past the hardware FIFO into adjacent controller state\\u2014treated as High per OOB-write guidance.\\nA:H - Oversized transfers can fail, time out, or leave SPI controller/device state corrupted so subsequent I/O hangs or faults; when choosing between no availability impact and sustained device/controller denial of service, High is the more severe defensible rating.\"}]}], \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"f231ff38b7b23197013b437128d196710fe282da\", \"lessThan\": \"15ff1f17847c19174b260bd7dd0de33edcebd45e\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"f231ff38b7b23197013b437128d196710fe282da\", \"lessThan\": \"f5723cfc01932c7a8d5c78dbf7e067e537c91439\", \"versionType\": \"git\"}], \"programFiles\": [\"drivers/base/regmap/regmap-spi.c\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"5.16\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"5.16\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"5.19.9\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.19.*\"}, {\"status\": \"unaffected\", \"version\": \"6.0\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"drivers/base/regmap/regmap-spi.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/15ff1f17847c19174b260bd7dd0de33edcebd45e\"}, {\"url\": \"https://git.kernel.org/stable/c/f5723cfc01932c7a8d5c78dbf7e067e537c91439\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nregmap: spi: Reserve space for register address/padding\\n\\nCurrently the max_raw_read and max_raw_write limits in regmap_spi struct\\ndo not take into account the additional size of the transmitted register\\naddress and padding.  This may result in exceeding the maximum permitted\\nSPI message size, which could cause undefined behaviour, e.g. data\\ncorruption.\\n\\nFix regmap_get_spi_bus() to properly adjust the above mentioned limits\\nby reserving space for the register address/padding as set in the regmap\\nconfiguration.\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"5.19.9\", \"versionStartIncluding\": \"5.16\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.0\", \"versionStartIncluding\": \"5.16\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-08-05T08:51:49.444Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2022-48696\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-08-05T08:51:49.444Z\", \"dateReserved\": \"2024-05-03T14:55:07.145Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-05-03T15:09:48.280Z\", \"assignerShortName\": \"Linux\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…