# CVE-2024-46859: platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses

> A missing bounds check in the Panasonic laptop kernel driver allows out-of-bounds array access, potentially causing a system crash or denial of service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Sep 2024
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-49884, AZL-49890, BELL-CVE-2024-46859, DEBIAN-CVE-2024-46859, GHSA-r56c-c546-6wvj, ROOT-OS-DEBIAN-11-CVE-2024-46859, UBUNTU-CVE-2024-46859

## What is CVE-2024-46859?

CVE-2024-46859 is a high-severity vulnerability in Debian Debian Linux, published on 27 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses

The panasonic laptop code in various places uses the SINF array with index
values of 0 - SINF_CUR_BRIGHT(0x0d) without checking that the SINF array
is big enough.

Not all panasonic laptops have this many SINF array entries, for example
the Toughbook CF-18 model only has 10 SINF array entries. So it only
supports the AC+DC brightness entries and mute.

Check that the SINF array has a minimum size which covers all AC+DC
brightness entries and refuse to load if the SINF array is smaller.

For higher SINF indexes hide the sysfs attributes when the SINF array
does not contain an entry for that attribute, avoiding show()/store()
accessing the array out of bounds and add bounds checking to the probe()
and resume() code accessing these.

Weakness: CWE-129 (Improper Validation of Array Index)

## Which versions are affected by CVE-2024-46859?

It affects 2 products.


Products: Debian Debian Linux, Linux kernel.

## How do I fix CVE-2024-46859?

Apply the vendor's patch.

## Is CVE-2024-46859 being exploited?

There is no known exploitation of CVE-2024-46859 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-46859 and fix it if it is affected.

What it is: CVE-2024-46859 is a high-severity vulnerability in Debian Debian Linux, published on 27 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-46859 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-46859/ (Markdown: https://insights.sbomify.com/CVE-2024-46859/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-46859
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-46859
- OSV: https://osv.dev/vulnerability/CVE-2024-46859

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-46859/
Summaries are generated and may contain mistakes; the official description above is the record.