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
F173189464: D10377.id.diff
Thu, Sep 24, 4:43 AM
F173181373: D10377.diff
Thu, Sep 24, 3:46 AM
Unknown Object (File)
Wed, Sep 23, 2:43 AM
Unknown Object (File)
Thu, Sep 10, 11:08 PM
Unknown Object (File)
Fri, Sep 4, 5:20 AM
Unknown Object (File)
Fri, Aug 28, 1:00 AM
Unknown Object (File)
Aug 12 2026, 12:50 PM
Unknown Object (File)
Aug 12 2026, 12:49 PM
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.