linux-kernel - Re: [PATCH] misc: ds1682: fix out-of-bounds access in EEPROM functions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+LcPJ1jSPOCp7Tr-tsy9aGirPtP7-FXTr=qnLjfHeo-T1u_tw@mail.gmail.com>
Date: Sun, 10 Aug 2025 05:47:05 +0500
From: wajahat iqbal <wajahatiqbal22@...il.com>
To: gregkh@...uxfoundation.org
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH] misc: ds1682: fix out-of-bounds access in EEPROM functions

Hi again,

Just to add, while sysfs enforces size limits, these only protect
accesses through the sysfs interface. Adding explicit bounds checks in
the driver helps ensure safety if the functions are called from
elsewhere or future code changes bypass sysfs checks.

This extra layer helps avoid potential hardware issues or crashes due
to out-of-bounds access.

Thanks again for reviewing.

Best,

Wajahat