Page MenuHomeFreeBSD

Fix an out-of-bounds write when a zero-length buffer is passed.
ClosedPublic

Authored by brooks on Apr 12 2017, 10:57 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Jan 17, 7:43 PM
Unknown Object (File)
Sat, Jan 10, 2:32 AM
Unknown Object (File)
Fri, Jan 9, 1:06 AM
Unknown Object (File)
Dec 17 2025, 2:59 AM
Unknown Object (File)
Dec 16 2025, 1:03 PM
Unknown Object (File)
Nov 21 2025, 6:29 AM
Unknown Object (File)
Nov 21 2025, 6:28 AM
Unknown Object (File)
Nov 21 2025, 6:12 AM
Subscribers
None

Details

Summary

Found with ttyname_test and CHERI bounds checking.

Sponsored by: DARPA, AFRL
Obtained from: CheriBSD

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

I also wonder if we should perform a NULL pointer check, but POSIX doesn't explicitly allow EINVAL.

This revision is now accepted and ready to land.Apr 12 2017, 11:10 PM

I also wonder if we should perform a NULL pointer check, but POSIX doesn't explicitly allow EINVAL.

Bruce would argue that a SIGSEGV is a valid NULL pointer check. That is the failure case for many other APIs in userland (e.g. strlen() and strcpy()).

This revision was automatically updated to reflect the committed changes.