GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Check your stack
CVE-2026-99190unknown

gpiolib: fix memory leak in gpiod_set_array_value_complex() on error paths

Impact

In the Linux kernel, the following vulnerability has been resolved:

Source excerpt · Linux

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

Linux · Linux

Other versions: unaffected

Version / rangeSource status
9b407312755fd5db012413ca005f0f3a661db8dd to before 78189c0e35abbcdab3b8ab0b764d578c02900734affected
9b407312755fd5db012413ca005f0f3a661db8dd to before 890c3bf08e0fc09eff788a6cfeded7d21b4d3e9daffected
9b407312755fd5db012413ca005f0f3a661db8dd to before c28846ca1ac6134881114d272314623c8433e372affected
d73d2a569e6212f58d89efc6e66ffbb2386a47b1affected
6.12.114 to before 6.13affected
Linux version evidence

Linux · Linux

Other versions: affected

Version / rangeSource status
6.15affected
0 to before 6.15unaffected
6.18.59 through 6.18.* (inclusive)unaffected
7.2.13 through 7.2.* (inclusive)unaffected
7.3 through * (inclusive)unaffected
Linux version evidence

Original source description

In the Linux kernel, the following vulnerability has been resolved:

gpiolib: fix memory leak in gpiod_set_array_value_complex() on error paths

A drive-by review by Sashiko reports that, after a failed call to gpiochip_set_multiple(), gpiod_set_array_value() returns abruptly, bypassing the freeing of possibly alloced bitmaps, potentially leaking memory. It is an unlikely error path, but is possible.

Defer the return code check until after the bitmap_free() block.

References