Page MenuHomeFreeBSD

tarfs: Fix two input validation issues.
ClosedPublic

Authored by des on Feb 29 2024, 7:47 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Jun 22, 8:00 AM
Unknown Object (File)
Mon, Jun 3, 6:31 AM
Unknown Object (File)
May 26 2024, 2:55 PM
Unknown Object (File)
May 18 2024, 7:58 AM
Unknown Object (File)
May 18 2024, 4:49 AM
Unknown Object (File)
May 13 2024, 6:05 PM
Unknown Object (File)
May 2 2024, 10:18 PM
Unknown Object (File)
Apr 27 2024, 3:11 AM
Subscribers

Details

Summary
  • Reject hard or soft links with an empty target path. Currently, a debugging kernel will hit an assertion in tarfs_lookup_path() while a non-debugging kernel will happily create a link to the mount root.
  • Use a temporary variable to store the result of the link target path, and copy it to tnp->other only once we have found it to be valid. Otherwise we error out after creating a reference to the target but before incrementing the target's reference count, which results in a use-after-free situation in the cleanup code.
  • Correctly return ENOENT from tarfs_lookup_path() if the requested path was not found and create_dirs is false. Luckily, existing callers did not rely solely on the return value.

MFC after: 3 days
PR: 277360
Sponsored by: Juniper Networks, Inc.
Sponsored by: Klara, Inc.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

des requested review of this revision.Feb 29 2024, 7:47 PM

fix link to nonexistent target

This revision is now accepted and ready to land.Mar 1 2024, 9:48 PM
This revision was automatically updated to reflect the committed changes.