FKIE_CVE-2026-89866

Vulnerability from fkie_nvd - Published: 2026-09-16 11:16 - Updated: 2026-10-19 09:18
Severity
Summary
In the Linux kernel, the following vulnerability has been resolved: media: chips-media: wave5: Resume device before setting EOS flag Setting the EOS flag talks to the firmware via send_firmware_command(), which accesses VPU registers. Both the STREAMOFF path (wave5_vpu_dec_job_abort()) and the V4L2_DEC_CMD_STOP path (wave5_vpu_dec_stop()) can run while the device is runtime suspended, so those register accesses hit powered-down hardware and the SoC raises an asynchronous SError, panicking the kernel: SError Interrupt on CPU3, code 0x00000000bf000000 -- SError send_firmware_command+0x2c/0x160 [wave5] wave5_vpu_dec_set_bitstream_flag+0x6c/0x80 [wave5] wave5_vpu_dec_update_bitstream_buffer+0x80/0xec [wave5] wave5_vpu_dec_job_abort+0x44/0xa0 [wave5] v4l2_m2m_cancel_job+0x110/0x19c [v4l2_mem2mem] v4l2_m2m_streamoff+0x24/0x140 [v4l2_mem2mem] Resume the device with pm_runtime_resume_and_get() around the EOS firmware command and release it with pm_runtime_put_autosuspend(), matching the runtime PM handling already done in wave5_vpu_dec_device_run().
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/2215e55ee1e5e69ad53862d968360c5aa63dd3a7
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/56c2c5ad35614ca5ae23838d6af5d7f59e3124dc
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/a52e6f7923c17a672135b485ffd96fbd72f46267
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/media/platform/chips-media/wave5/wave5-vpu-dec.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "56c2c5ad35614ca5ae23838d6af5d7f59e3124dc",
              "status": "affected",
              "version": "9707a6254a8a6b978bde811a44fe07d86c229d1c",
              "versionType": "git"
            },
            {
              "lessThan": "2215e55ee1e5e69ad53862d968360c5aa63dd3a7",
              "status": "affected",
              "version": "9707a6254a8a6b978bde811a44fe07d86c229d1c",
              "versionType": "git"
            },
            {
              "lessThan": "a52e6f7923c17a672135b485ffd96fbd72f46267",
              "status": "affected",
              "version": "9707a6254a8a6b978bde811a44fe07d86c229d1c",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/media/platform/chips-media/wave5/wave5-vpu-dec.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.8"
            },
            {
              "lessThan": "6.8",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.57",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: chips-media: wave5: Resume device before setting EOS flag\n\nSetting the EOS flag talks to the firmware via send_firmware_command(),\nwhich accesses VPU registers. Both the STREAMOFF path\n(wave5_vpu_dec_job_abort()) and the V4L2_DEC_CMD_STOP path\n(wave5_vpu_dec_stop()) can run while the device is runtime suspended, so\nthose register accesses hit powered-down hardware and the SoC raises an\nasynchronous SError, panicking the kernel:\n\n  SError Interrupt on CPU3, code 0x00000000bf000000 -- SError\n   send_firmware_command+0x2c/0x160 [wave5]\n   wave5_vpu_dec_set_bitstream_flag+0x6c/0x80 [wave5]\n   wave5_vpu_dec_update_bitstream_buffer+0x80/0xec [wave5]\n   wave5_vpu_dec_job_abort+0x44/0xa0 [wave5]\n   v4l2_m2m_cancel_job+0x110/0x19c [v4l2_mem2mem]\n   v4l2_m2m_streamoff+0x24/0x140 [v4l2_mem2mem]\n\nResume the device with pm_runtime_resume_and_get() around the EOS\nfirmware command and release it with pm_runtime_put_autosuspend(),\nmatching the runtime PM handling already done in\nwave5_vpu_dec_device_run()."
    }
  ],
  "id": "CVE-2026-89866",
  "lastModified": "2026-10-19T09:18:31.280",
  "metrics": {},
  "published": "2026-09-16T11:16:54.743",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/2215e55ee1e5e69ad53862d968360c5aa63dd3a7"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/56c2c5ad35614ca5ae23838d6af5d7f59e3124dc"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/a52e6f7923c17a672135b485ffd96fbd72f46267"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.