high CVSS 7.8

CVE-2024-46859·Kernel vulnerability

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.

Severity
high
Software
Kernel
Fixed in
6.10.11
Published
2024-09-27

Affected versions

From: 6.7

Until: 6.10.11

Fixed in: 6.10.11

How to fix this CVE

Update your Linux kernel to version 6.10.11 or later to resolve an array bounds checking issue in the Panasonic laptop platform driver. This vulnerability could allow local attackers with user privileges to trigger kernel memory access violations. Systems running kernel versions 6.7 through 6.10.10 should prioritize this patch to prevent potential denial of service or privilege escalation.

sudo dnf update kernel kernel-devel

Defensia detects this vulnerability

How to check if you are affected

  1. Check your kernel version with: uname -r — compare against vulnerable range 6.7 through 6.10.10
  2. Verify if panasonic-laptop driver is loaded: lsmod | grep panasonic — if output is empty, system is not at risk from this specific driver flaw
  3. Search kernel logs for panasonic-laptop driver errors: dmesg | grep panasonic or journalctl -g panasonic — look for out-of-bounds warnings or SINF array errors
  4. After updating, confirm the fix with uname -r — should show 6.10.11 or later, then reboot if needed: sudo reboot

FAQ

What is CVE-2024-46859?

This vulnerability exists in the Linux kernel's Panasonic laptop platform driver, where array bounds checking is missing when accessing the SINF (System Information) array. Certain laptop models have fewer SINF entries than the code expects, leading to out-of-bounds memory access when the driver tries to read non-existent array indices.

Is CVE-2024-46859 being actively exploited?

No, this vulnerability is not listed in CISA's Known Exploited Vulnerabilities (KEV) catalog and no public exploits are currently available. However, local attackers with user privileges could trigger it on vulnerable Panasonic laptops.

What versions of Kernel are affected by CVE-2024-46859?

Linux kernel versions 6.7.0 through 6.10.10 are vulnerable. Kernel 6.10.11 and later contain the fix.

How do I check if my server is vulnerable to CVE-2024-46859?

Run uname -r to check your kernel version — if it shows 6.7.x through 6.10.10, you are vulnerable. Additionally, check if the panasonic-laptop driver is active with: lsmod | grep panasonic — vulnerability only applies if this driver is loaded.

Does Defensia detect CVE-2024-46859?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Linux kernel is installed on a monitored server within the vulnerable version range, CVE-2024-46859 will appear in your dashboard with remediation steps.

Related Kernel CVEs

CVE-2024-42256CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: cifs: Fix server re-repick on subrequest retry When a subrequest is marked for needing retry, netfs will call cifs_prepare_write() which will make cifs repick the server for the op before renegotiating credits; it then calls cifs_issue_write() which invokes smb2_async_writev() - which re-repicks the server. If a different server is then selected, this causes the increment of server->in_flight to happen against one record and the decrement to happen against another, leading to misaccounting. Fix this by just removing the repick code in smb2_async_writev(). As this is only called from netfslib-driven code, cifs_prepare_write() should always have been called first, and so server should never be NULL and the preparatory step is repeated in the event that we do a retry. The problem manifests as a warning looking something like: WARNING: CPU: 4 PID: 72896 at fs/smb/client/smb2ops.c:97 smb2_add_credits+0x3f0/0x9e0 [cifs] ... RIP: 0010:smb2_add_credits+0x3f0/0x9e0 [cifs] ... smb2_writev_callback+0x334/0x560 [cifs] cifs_demultiplex_thread+0x77a/0x11b0 [cifs] kthread+0x187/0x1d0 ret_from_fork+0x34/0x60 ret_from_fork_asm+0x1a/0x30 Which may be triggered by a number of different xfstests running against an Azure server in multichannel mode. generic/249 seems the most repeatable, but generic/215, generic/249 and generic/308 may also show it.
CVE-2024-36031CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: keys: Fix overwrite of key expiration on instantiation The expiry time of a key is unconditionally overwritten during instantiation, defaulting to turn it permanent. This causes a problem for DNS resolution as the expiration set by user-space is overwritten to TIME64_MAX, disabling further DNS updates. Fix this by restoring the condition that key_set_expiry is only called when the pre-parser sets a specific expiry.
CVE-2024-38612CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ipv6: sr: fix invalid unregister error path The error path of seg6_init() is wrong in case CONFIG_IPV6_SEG6_LWTUNNEL is not defined. In that case if seg6_hmac_init() fails, the genl_unregister_family() isn't called. This issue exist since commit 46738b1317e1 ("ipv6: sr: add option to control lwtunnel support"), and commit 5559cea2d5aa ("ipv6: sr: fix possible use-after-free and null-ptr-deref") replaced unregister_pernet_subsys() with genl_unregister_family() in this error path.
CVE-2024-38623CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Use variable length array instead of fixed size Should fix smatch warning: ntfs_set_label() error: __builtin_memcpy() 'uni->name' too small (20 vs 256)
CVE-2021-47548CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port() The if statement: if (port >= DSAF_GE_NUM) return; limits the value of port less than DSAF_GE_NUM (i.e., 8). However, if the value of port is 6 or 7, an array overflow could occur: port_rst_off = dsaf_dev->mac_cb[port]->port_rst_off; because the length of dsaf_dev->mac_cb is DSAF_MAX_PORT_NUM (i.e., 6). To fix this possible array overflow, we first check port and if it is greater than or equal to DSAF_MAX_PORT_NUM, the function returns.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-46859. Free for 1 server.

Get started free