There is one obvious syntax error, one functionality error, and one change I strongly recommend.
Recommended change
On the line where you call eval, do not call eval on a symbolic expression. [You should avoid calling eval anywhere on general principles but certainly don't call it on a symbolic expression.] If you need the symbolic result to be converted to a number, call double on it instead. That is the change I strongly recommend.
Syntax error
On that same line of code you have a syntax error. Let's count parentheses, starting at 0 at the start of the line. Add 1 when you see a ( and subtract 1 when you see a ). If the count at the end of the line is not 0, you have mismatched parentheses, more ( than ). If the count ever goes negative, you have more ) than ( and that's an error as well.
x1 = eval(x0 - fx(x0)/df(x0);
You're missing a ). Fix that when you replace eval with double. That's the syntax error.
Note that if you open the file in the MATLAB Editor, Code Analyzer will flag that line with a red error message indicating a problem that likely will prevent your code from executing and will tell you (in a shorter sentence) what I said.
Functionality error
Once you do that, MATLAB will still complain on this line. You may expect fx(x0) to evaluate the function fx at x0 but fx is not a function. It is a symbolic expression. To substitute values into a symbolic expression use the subs function.
Alternately you could convert the symbolic expression into an anonymous function using the matlabFunction function. Anonymous functions can be evaluated using that syntax. Note that if you do this you won't be able to perform symbolic-only operations (like diff, which you could have used to generate df from fx) on the anonymous function. That fixes the functionality error.
Suggestion for the future
One suggestion for the future: when asking for help here with code that "doesn't work", throws an error, or issues a warning, please provide information about the specific behavior that's not working as you expect or is throwing an error. Including the full and exact text of the error and/or warning messages (all the text displayed in red or orange) will help with identifying the cause of the error and/or warning. The easier you make it for people to investigate the more likely they'll be to help.
