FKIE_CVE-2026-23092

Vulnerability from fkie_nvd - Published: 2026-02-04 17:16 - Updated: 2026-02-05 14:57
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: iio: dac: ad3552r-hs: fix out-of-bound write in ad3552r_hs_write_data_source When simple_write_to_buffer() succeeds, it returns the number of bytes actually copied to the buffer. The code incorrectly uses 'count' as the index for null termination instead of the actual bytes copied. If count exceeds the buffer size, this leads to out-of-bounds write. Add a check for the count and use the return value as the index. The bug was validated using a demo module that mirrors the original code and was tested under QEMU. Pattern of the bug: - A fixed 64-byte stack buffer is filled using count. - If count > 64, the code still does buf[count] = '\0', causing an - out-of-bounds write on the stack. Steps for reproduce: - Opens the device node. - Writes 128 bytes of A to it. - This overflows the 64-byte stack buffer and KASAN reports the OOB. Found via static analysis. This is similar to the commit da9374819eb3 ("iio: backend: fix out-of-bound write")
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/978d28136c53df38f8f0b747191930e2f95e9084
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/db16e7c52032c79156930a337ee17232931794ba
Impacted products
Vendor Product Version
To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\niio: dac: ad3552r-hs: fix out-of-bound write in ad3552r_hs_write_data_source\n\nWhen simple_write_to_buffer() succeeds, it returns the number of bytes\nactually copied to the buffer. The code incorrectly uses \u0027count\u0027\nas the index for null termination instead of the actual bytes copied.\nIf count exceeds the buffer size, this leads to out-of-bounds write.\nAdd a check for the count and use the return value as the index.\n\nThe bug was validated using a demo module that mirrors the original\ncode and was tested under QEMU.\n\nPattern of the bug:\n- A fixed 64-byte stack buffer is filled using count.\n- If count \u003e 64, the code still does buf[count] = \u0027\\0\u0027, causing an\n- out-of-bounds write on the stack.\n\nSteps for reproduce:\n- Opens the device node.\n- Writes 128 bytes of A to it.\n- This overflows the 64-byte stack buffer and KASAN reports the OOB.\n\nFound via static analysis. This is similar to the\ncommit da9374819eb3 (\"iio: backend: fix out-of-bound write\")"
    },
    {
      "lang": "es",
      "value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\niio: dac: ad3552r-hs: correcci\u00f3n de escritura fuera de l\u00edmites en ad3552r_hs_write_data_source\n\nCuando simple_write_to_buffer() tiene \u00e9xito, devuelve el n\u00famero de bytes realmente copiados al b\u00fafer. El c\u00f3digo usa incorrectamente \u0027count\u0027 como \u00edndice para la terminaci\u00f3n nula en lugar de los bytes realmente copiados. Si count excede el tama\u00f1o del b\u00fafer, esto lleva a una escritura fuera de l\u00edmites. A\u00f1adir una comprobaci\u00f3n para count y usar el valor de retorno como \u00edndice.\n\nEl error fue validado usando un m\u00f3dulo de demostraci\u00f3n que refleja el c\u00f3digo original y fue probado bajo QEMU.\n\nPatr\u00f3n del error:\n- Un b\u00fafer de pila fijo de 64 bytes se llena usando count.\n- Si count \u0026gt; 64, el c\u00f3digo a\u00fan hace buf[count] = \u0027\\0\u0027, causando una\n- escritura fuera de l\u00edmites en la pila.\n\nPasos para reproducir:\n- Abre el nodo del dispositivo.\n- Escribe 128 bytes de A en \u00e9l.\n- Esto desborda el b\u00fafer de pila de 64 bytes y KASAN reporta el OOB.\n\nEncontrado mediante an\u00e1lisis est\u00e1tico. Esto es similar al\ncommit da9374819eb3 (\u0027iio: backend: correcci\u00f3n de escritura fuera de l\u00edmites\u0027)"
    }
  ],
  "id": "CVE-2026-23092",
  "lastModified": "2026-02-05T14:57:20.563",
  "metrics": {},
  "published": "2026-02-04T17:16:20.083",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/978d28136c53df38f8f0b747191930e2f95e9084"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/db16e7c52032c79156930a337ee17232931794ba"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Awaiting Analysis"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

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.



Detection rules are retrieved from Rulezet.